/* * Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved. * * Licensed under the Apache License, Version 2.0 (the "License"). * You may not use this file except in compliance with the License. * A copy of the License is located at * * http://aws.amazon.com/apache2.0 * * or in the "license" file accompanying this file. This file is distributed * on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either * express or implied. See the License for the specific language governing * permissions and limitations under the License. */ /* * Do not modify this file. This file is generated from the eks-2017-11-01.normal.json service model. */ using System; using System.Collections.Generic; using System.Xml.Serialization; using System.Text; using System.IO; using System.Net; using Amazon.Runtime; using Amazon.Runtime.Internal; namespace Amazon.EKS.Model { /// /// An object representing an issue with an Amazon EKS resource. /// public partial class Issue { private NodegroupIssueCode _code; private string _message; private List _resourceIds = new List(); /// /// Gets and sets the property Code. /// /// A brief description of the error. /// ///
  • /// /// AccessDenied: Amazon EKS or one or more of your managed nodes is failing to /// authenticate or authorize with your Kubernetes cluster API server. /// ///
  • /// /// AsgInstanceLaunchFailures: Your Auto Scaling group is experiencing failures /// while attempting to launch instances. /// ///
  • /// /// AutoScalingGroupNotFound: We couldn't find the Auto Scaling group associated /// with the managed node group. You may be able to recreate an Auto Scaling group with /// the same settings to recover. /// ///
  • /// /// ClusterUnreachable: Amazon EKS or one or more of your managed nodes is unable /// to to communicate with your Kubernetes cluster API server. This can happen if there /// are network disruptions or if API servers are timing out processing requests. /// ///
  • /// /// Ec2LaunchTemplateNotFound: We couldn't find the Amazon EC2 launch template /// for your managed node group. You may be able to recreate a launch template with the /// same settings to recover. /// ///
  • /// /// Ec2LaunchTemplateVersionMismatch: The Amazon EC2 launch template version for /// your managed node group does not match the version that Amazon EKS created. You may /// be able to revert to the version that Amazon EKS created to recover. /// ///
  • /// /// Ec2SecurityGroupDeletionFailure: We could not delete the remote access security /// group for your managed node group. Remove any dependencies from the security group. /// ///
  • /// /// Ec2SecurityGroupNotFound: We couldn't find the cluster security group for /// the cluster. You must recreate your cluster. /// ///
  • /// /// Ec2SubnetInvalidConfiguration: One or more Amazon EC2 subnets specified for /// a node group do not automatically assign public IP addresses to instances launched /// into it. If you want your instances to be assigned a public IP address, then you need /// to enable the auto-assign public IP address setting for the subnet. See /// Modifying /// the public IPv4 addressing attribute for your subnet in the Amazon VPC User /// Guide. /// ///
  • /// /// IamInstanceProfileNotFound: We couldn't find the IAM instance profile for /// your managed node group. You may be able to recreate an instance profile with the /// same settings to recover. /// ///
  • /// /// IamNodeRoleNotFound: We couldn't find the IAM role for your managed node group. /// You may be able to recreate an IAM role with the same settings to recover. /// ///
  • /// /// InstanceLimitExceeded: Your Amazon Web Services account is unable to launch /// any more instances of the specified instance type. You may be able to request an Amazon /// EC2 instance limit increase to recover. /// ///
  • /// /// InsufficientFreeAddresses: One or more of the subnets associated with your /// managed node group does not have enough available IP addresses for new nodes. /// ///
  • /// /// InternalFailure: These errors are usually caused by an Amazon EKS server-side /// issue. /// ///
  • /// /// NodeCreationFailure: Your launched instances are unable to register with your /// Amazon EKS cluster. Common causes of this failure are insufficient node /// IAM role permissions or lack of outbound internet access for the nodes. /// ///
///
public NodegroupIssueCode Code { get { return this._code; } set { this._code = value; } } // Check to see if Code property is set internal bool IsSetCode() { return this._code != null; } /// /// Gets and sets the property Message. /// /// The error message associated with the issue. /// /// public string Message { get { return this._message; } set { this._message = value; } } // Check to see if Message property is set internal bool IsSetMessage() { return this._message != null; } /// /// Gets and sets the property ResourceIds. /// /// The Amazon Web Services resources that are afflicted by this issue. /// /// public List ResourceIds { get { return this._resourceIds; } set { this._resourceIds = value; } } // Check to see if ResourceIds property is set internal bool IsSetResourceIds() { return this._resourceIds != null && this._resourceIds.Count > 0; } } }