Error message: 'You have not accepted the legal terms on this subscription: '*********' for this plan. Running tanzu mc create or tanzu cluster create without having accepted the license fails with an error like: User failed validation to purchase resources. Failed Validation, Legal Terms Error on Azureīefore creating a management or workload cluster on Azure, you must accept the legal terms that cover the VM image used by cluster nodes. Before creating a management or a workload cluster on AWS, you must configure your AWS account credentials as described in Configure AWS Credentials. Tanzu Kubernetes Grid uses the default AWS credentials provider chain. SharedCredsLoad: failed to load shared credentials fileĬaused by: FailedRead: unable to open fileĬaused by: open /root/.aws/credentials: no such file or directoryĮC2RoleRequestError: no EC2 instance role foundĬaused by: EC2MetadataError: failed to make EC2Metadata request Looking for AWS credentials in the default credentials provider chainĮrror: : Tkg configuration validation failed: failed to get AWS client: NoCredentialProviders: no valid providers in chainĬaused by: EnvAccessKeyNotFound: AWS_ACCESS_KEY_ID or AWS_ACCESS_KEY not found in environment Running tanzu management-cluster create or tanzu mc create fails with an error similar to the following: Validating the pre-requisites. Infrastructure Provider Failed Validation, Credentials Error on AWS To deactivate nfs-utils on clusters that you deploy with Tanzu Kubernetes Grid v1.1.2 or later, use SSH to log in to the cluster node VMs and run the following command: tdnf erase nfs-utils If you do not require nfs-utils, you can remove it from cluster node VMs. In Tanzu Kubernetes Grid v1.1.2 and later, nfs-utils is enabled by default. To see the management clusters that the tanzu CLI tracks, run tanzu login.If you deleted management clusters that are tracked by the tanzu CLI, delete them from the tanzu CLI’s state by running tanzu config server delete as described in Delete Management Clusters from Your Tanzu CLI Configuration. ![]() Kubectl config unset current-context -kubeconfig ~/.kube-tkg/config If the config files list the current context as a cluster that you deleted, unset the context: kubectl config unset current-context ![]() Where CLUSTER-NAME is the name property of each top-level cluster object, as listed in the config files. Kubectl config unset clusters.CLUSTER-NAME -kubeconfig ~/.kube-tkg/config Where CONTEXT-NAME is the name property of each top-level context object, as listed in the config files, typically of the form the cluster objects that you want to delete, run: kubectl config unset clusters.CLUSTER-NAME Kubectl config unset contexts.CONTEXT-NAME -kubeconfig ~/.kube-tkg/config Where USER-NAME is the name property of each top-level user object, as listed in the config files.įor the context objects that you want to delete, run: kubectl config unset contexts.CONTEXT-NAME Kubectl config unset users.USER-NAME -kubeconfig ~/.kube-tkg/config Open your ~/.kube/config and ~/.kube-tkg/config files.įor the user objects that you want to delete, run: kubectl config unset users.USER-NAME To clean up your kubectl state by deleting some or all of its users, contexts, and clusters: Delete Users, Contexts, and Clusters with kubectl AWS management cluster and Tanzu Kubernetes nodes running on Amazon Linux: ssh node_addressīecause the SSH key is present on the system on which you are running the ssh command, no password is required.AWS bastion nodes and management cluster and workload nodes on Ubuntu: ssh node_address.To connect to a node by using SSH, run one of the following commands from the machine that you use as the bootstrap machine: Azure management cluster and Tanzu Kubernetes nodes (always Ubuntu): capi.AWS management cluster and Tanzu Kubernetes nodes running on Amazon Linux: ec2-user.AWS management cluster and Tanzu Kubernetes nodes running on Ubuntu: ubuntu. ![]()
0 Comments
Leave a Reply. |