com.amazonaws.services.eks.model.Issue Maven / Gradle / Ivy
/*
* Copyright 2018-2023 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.
*/
package com.amazonaws.services.eks.model;
import java.io.Serializable;
import javax.annotation.Generated;
import com.amazonaws.protocol.StructuredPojo;
import com.amazonaws.protocol.ProtocolMarshaller;
/**
*
* An object representing an issue with an Amazon EKS resource.
*
*
* @see AWS API Documentation
*/
@Generated("com.amazonaws:aws-java-sdk-code-generator")
public class Issue implements Serializable, Cloneable, StructuredPojo {
/**
*
* 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.
*
*
*
*/
private String code;
/**
*
* The error message associated with the issue.
*
*/
private String message;
/**
*
* The Amazon Web Services resources that are afflicted by this issue.
*
*/
private java.util.List resourceIds;
/**
*
* 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.
*
*
*
*
* @param 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.
*
*
* @see NodegroupIssueCode
*/
public void setCode(String code) {
this.code = 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.
*
*
*
*
* @return 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.
*
*
* @see NodegroupIssueCode
*/
public String getCode() {
return this.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.
*
*
*
*
* @param 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.
*
*
* @return Returns a reference to this object so that method calls can be chained together.
* @see NodegroupIssueCode
*/
public Issue withCode(String code) {
setCode(code);
return this;
}
/**
*
* 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.
*
*
*
*
* @param 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.
*
*
* @return Returns a reference to this object so that method calls can be chained together.
* @see NodegroupIssueCode
*/
public Issue withCode(NodegroupIssueCode code) {
this.code = code.toString();
return this;
}
/**
*
* The error message associated with the issue.
*
*
* @param message
* The error message associated with the issue.
*/
public void setMessage(String message) {
this.message = message;
}
/**
*
* The error message associated with the issue.
*
*
* @return The error message associated with the issue.
*/
public String getMessage() {
return this.message;
}
/**
*
* The error message associated with the issue.
*
*
* @param message
* The error message associated with the issue.
* @return Returns a reference to this object so that method calls can be chained together.
*/
public Issue withMessage(String message) {
setMessage(message);
return this;
}
/**
*
* The Amazon Web Services resources that are afflicted by this issue.
*
*
* @return The Amazon Web Services resources that are afflicted by this issue.
*/
public java.util.List getResourceIds() {
return resourceIds;
}
/**
*
* The Amazon Web Services resources that are afflicted by this issue.
*
*
* @param resourceIds
* The Amazon Web Services resources that are afflicted by this issue.
*/
public void setResourceIds(java.util.Collection resourceIds) {
if (resourceIds == null) {
this.resourceIds = null;
return;
}
this.resourceIds = new java.util.ArrayList(resourceIds);
}
/**
*
* The Amazon Web Services resources that are afflicted by this issue.
*
*
* NOTE: This method appends the values to the existing list (if any). Use
* {@link #setResourceIds(java.util.Collection)} or {@link #withResourceIds(java.util.Collection)} if you want to
* override the existing values.
*
*
* @param resourceIds
* The Amazon Web Services resources that are afflicted by this issue.
* @return Returns a reference to this object so that method calls can be chained together.
*/
public Issue withResourceIds(String... resourceIds) {
if (this.resourceIds == null) {
setResourceIds(new java.util.ArrayList(resourceIds.length));
}
for (String ele : resourceIds) {
this.resourceIds.add(ele);
}
return this;
}
/**
*
* The Amazon Web Services resources that are afflicted by this issue.
*
*
* @param resourceIds
* The Amazon Web Services resources that are afflicted by this issue.
* @return Returns a reference to this object so that method calls can be chained together.
*/
public Issue withResourceIds(java.util.Collection resourceIds) {
setResourceIds(resourceIds);
return this;
}
/**
* Returns a string representation of this object. This is useful for testing and debugging. Sensitive data will be
* redacted from this string using a placeholder value.
*
* @return A string representation of this object.
*
* @see java.lang.Object#toString()
*/
@Override
public String toString() {
StringBuilder sb = new StringBuilder();
sb.append("{");
if (getCode() != null)
sb.append("Code: ").append(getCode()).append(",");
if (getMessage() != null)
sb.append("Message: ").append(getMessage()).append(",");
if (getResourceIds() != null)
sb.append("ResourceIds: ").append(getResourceIds());
sb.append("}");
return sb.toString();
}
@Override
public boolean equals(Object obj) {
if (this == obj)
return true;
if (obj == null)
return false;
if (obj instanceof Issue == false)
return false;
Issue other = (Issue) obj;
if (other.getCode() == null ^ this.getCode() == null)
return false;
if (other.getCode() != null && other.getCode().equals(this.getCode()) == false)
return false;
if (other.getMessage() == null ^ this.getMessage() == null)
return false;
if (other.getMessage() != null && other.getMessage().equals(this.getMessage()) == false)
return false;
if (other.getResourceIds() == null ^ this.getResourceIds() == null)
return false;
if (other.getResourceIds() != null && other.getResourceIds().equals(this.getResourceIds()) == false)
return false;
return true;
}
@Override
public int hashCode() {
final int prime = 31;
int hashCode = 1;
hashCode = prime * hashCode + ((getCode() == null) ? 0 : getCode().hashCode());
hashCode = prime * hashCode + ((getMessage() == null) ? 0 : getMessage().hashCode());
hashCode = prime * hashCode + ((getResourceIds() == null) ? 0 : getResourceIds().hashCode());
return hashCode;
}
@Override
public Issue clone() {
try {
return (Issue) super.clone();
} catch (CloneNotSupportedException e) {
throw new IllegalStateException("Got a CloneNotSupportedException from Object.clone() " + "even though we're Cloneable!", e);
}
}
@com.amazonaws.annotation.SdkInternalApi
@Override
public void marshall(ProtocolMarshaller protocolMarshaller) {
com.amazonaws.services.eks.model.transform.IssueMarshaller.getInstance().marshall(this, protocolMarshaller);
}
}