Is it expected behavior that upgrading an AKS clus...
# kubernetesf
famous-jelly-72366
06/10/2020, 9:51 AMIs it expected behavior that upgrading an AKS cluster will replace all resources ???
famous-jelly-72366
06/10/2020, 10:10 AMok seems this is only the case during preview ... when actually applying, it does as expected 🙂
g
gentle-diamond-70147
06/10/2020, 3:23 PMCan you provide the preview and apply output?
f
famous-jelly-72366
06/11/2020, 4:21 AMunfortunately I already applied the upgrade :S But what happened was that during the preview phase it detected that it should update the cluster (correct to upgrade the version from 1.15 to 1.16), but it also listed all my k8s resources to be replaced (namespaces, helm charts with ext-dns, nginx, cert-manager etc).
famous-jelly-72366
06/11/2020, 4:22 AMhowever when I applied it, all it did what update the cluster - which was the expected result. no k8s resources were replaced
famous-jelly-72366
06/11/2020, 2:30 PMI'm doing another upgrade (from 1.16.9 > 1.17.5), here is what pulumi up shows during preview:
Copy code
› pulumi up
Previewing update (k8s):
Type Name
pulumi:pulumi:Stack tms-pulumi-k8s
~ ├─ azure:containerservice:KubernetesCluster k8s-dev-Cluster
+- ├─ pulumi:providers:kubernetes k8s-dev-Provider
+- ├─ kubernetes:core:Namespace app-services
+- ├─ kubernetes:<http://rbac.authorization.k8s.io:ClusterRoleBinding|rbac.authorization.k8s.io:ClusterRoleBinding> pulumi-admins
+- ├─ kubernetes:core:Namespace apps
+- ├─ kubernetes:<http://rbac.authorization.k8s.io:Role|rbac.authorization.k8s.io:Role> pulumi-devs-apps
+- ├─ kubernetes:<http://rbac.authorization.k8s.io:RoleBinding|rbac.authorization.k8s.io:RoleBinding> pulumi-devs-apps
├─ kubernetes:helm.sh:Chart k8s-dev-ingress
+- │ ├─ kubernetes:core:ServiceAccount app-services/k8s-dev-ingressg
gentle-diamond-70147
06/11/2020, 4:03 PMCan you provide the
preview --difff
famous-jelly-72366
06/12/2020, 7:46 AMI already completed the upgrade ... mayb enext time 😄
3 Views