Updated Kubernetes version to 1.24.10 #2790
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
etungsten
approved these changes
Feb 14, 2023
There was a problem hiding this comment.
Built aws-k8s-1.24 AMI and nodes join cluster and run pods fine:
$ kubectl get nodes -o wide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
ip-192-168-13-252.us-west-2.compute.internal Ready <none> 82s v1.24.10-eks-08ad9cc 192.168.13.252 54.187.125.248 Bottlerocket OS 1.12.0 (aws-k8s-1.24) 5.15.79 containerd://1.6.15+bottlerocket
ip-192-168-29-74.us-west-2.compute.internal Ready <none> 65s v1.24.10-eks-08ad9cc 192.168.29.74 54.190.58.84 Bottlerocket OS 1.12.0 (aws-k8s-1.24) 5.15.79 containerd://1.6.15+bottlerocket
$ kubectl get pods -o wide -A
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
default csi-secrets-store-secrets-store-csi-driver-j5697 0/3 ContainerCreating 0 7s <none> ip-192-168-13-252.us-west-2.compute.internal <none> <none>
default csi-secrets-store-secrets-store-csi-driver-ktlnd 3/3 Running 0 41s 192.168.28.1 ip-192-168-29-74.us-west-2.compute.internal <none> <none>
kube-system aws-node-rzqtf 1/1 Running 0 71s 192.168.29.74 ip-192-168-29-74.us-west-2.compute.internal <none> <none>
kube-system aws-node-xwknq 1/1 Running 0 88s 192.168.13.252 ip-192-168-13-252.us-west-2.compute.internal <none> <none>
kube-system coredns-559b5db75d-72fkk 1/1 Running 0 12m 192.168.15.178 ip-192-168-29-74.us-west-2.compute.internal <none> <none>
kube-system coredns-559b5db75d-ld5wk 1/1 Running 0 12m 192.168.30.196 ip-192-168-29-74.us-west-2.compute.internal <none> <none>
kube-system ebs-csi-controller-985774447-vrfgk 6/6 Running 0 12m 192.168.13.248 ip-192-168-29-74.us-west-2.compute.internal <none> <none>
kube-system ebs-csi-controller-985774447-zcz9j 6/6 Running 0 12m 192.168.2.101 ip-192-168-29-74.us-west-2.compute.internal <none> <none>
kube-system ebs-csi-node-kspgf 3/3 Running 0 41s 192.168.31.54 ip-192-168-29-74.us-west-2.compute.internal <none> <none>
kube-system ebs-csi-node-qlpqs 0/3 ContainerCreating 0 7s <none> ip-192-168-13-252.us-west-2.compute.internal <none> <none>
kube-system kube-proxy-5qq8n 1/1 Running 0 71s 192.168.29.74 ip-192-168-29-74.us-west-2.compute.internal <none> <none>
kube-system kube-proxy-c5k45 1/1 Running 0 88s 192.168.13.252 ip-192-168-13-252.us-west-2.compute.internal <none> <none>
stmcginnis
approved these changes
Feb 14, 2023
There was a problem hiding this comment.
Looks good!
$ k get nodes
NAME STATUS ROLES AGE VERSION
ip-192-168-21-51.us-east-2.compute.internal Ready <none> 48m v1.24.10-eks-08ad9cc
ip-192-168-34-197.us-east-2.compute.internal Ready <none> 48m v1.24.10-eks-08ad9cc
$ k get all -A
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system pod/aws-node-rk4q6 1/1 Running 0 76m
kube-system pod/aws-node-srnqc 1/1 Running 0 76m
kube-system pod/coredns-5c5677bc78-8v8md 1/1 Running 0 86m
kube-system pod/coredns-5c5677bc78-zwbxd 1/1 Running 0 86m
kube-system pod/kube-proxy-5tk95 1/1 Running 0 76m
kube-system pod/kube-proxy-82wmv 1/1 Running 0 76m
NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
default service/kubernetes ClusterIP 10.100.0.1 <none> 443/TCP 87m
kube-system service/kube-dns ClusterIP 10.100.0.10 <none> 53/UDP,53/TCP 87m
NAMESPACE NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
kube-system daemonset.apps/aws-node 2 2 2 2 2 <none> 87m
kube-system daemonset.apps/kube-proxy 2 2 2 2 2 <none> 87m
NAMESPACE NAME READY UP-TO-DATE AVAILABLE AGE
kube-system deployment.apps/coredns 2/2 2 2 87m
NAMESPACE NAME DESIRED CURRENT READY AGE
kube-system replicaset.apps/coredns-5c5677bc78 2 2 2 86m
$ k apply -f ../testing/test-pod.yaml
pod/webserver created
$ k get pods
NAME READY STATUS RESTARTS AGE
webserver 1/1 Running 0 6s
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue number:
Closes #
Description of changes:
Testing done:
Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.