Skip to content
This repository has been archived by the owner on Jun 28, 2023. It is now read-only.

Upgrade kapp-controller to 0.30 #2785

Closed
joshrosso opened this issue Jan 7, 2022 · 6 comments
Closed

Upgrade kapp-controller to 0.30 #2785

joshrosso opened this issue Jan 7, 2022 · 6 comments
Assignees
@joshrosso
Labels
kind/feature A request for a new feature owner/framework Work executed in vmware-tanzu/tanzu-framework owner/packages Work executed by a package's maintainer reporting/health/on-track
Milestone
v0.11.0

Comments

@joshrosso
Copy link
Contributor

This request was sourced in some capability work individuals want to bring into TCE.
@joshrosso joshrosso added owner/packages Work executed by a package's maintainer kind/feature A request for a new feature owner/framework Work executed in vmware-tanzu/tanzu-framework labels Jan 7, 2022
@joshrosso joshrosso added this to the v0.11.0 milestone Jan 7, 2022
@joshrosso
Copy link
Contributor Author

Current state of TCE kapp-controller is that we are bound to the versions shipped by our commercial product Tanzu Kubernetes Grid (TKG). We'll target this for the v0.11.0 release, currently aiming for the March timeframe.

@joshrosso joshrosso changed the title Upgrade kapp-controller to 0.35 Upgrade kapp-controller to 0.30 Jan 7, 2022
@kartiklunkad26 kartiklunkad26 mentioned this issue Feb 11, 2022
Closed
@seemiller
Copy link
Contributor

Current version of kapp-controller is 0.32.0, are we still locked to 0.30.0 in framework?

@joshrosso
Copy link
Contributor Author

I will investigate this today.

Due to #3275 (comment), we need to keep our BOM at the same version as v1.5.1. That will determine our kapp-controller version.

If it's below v0.30, this issue will be moved out to another milestone.

@joshrosso
Copy link
Contributor Author

This should be part of our next release. Our plan is is to pin to the TKG v1.5.1 BOM. Here is the evidence of the kapp-controller version:

tkr-compatibility:

version: v11
managementClusterVersions:
- version: v1.5.1
  supportedKubernetesVersions:
  - v1.22.5+vmware.1-tkg.3
  - v1.21.8+vmware.1-tkg.4
  - v1.20.14+vmware.1-tkg.4
- version: v1.5.0
  supportedKubernetesVersions:
  - v1.22.5+vmware.1-tkg.1
  - v1.21.8+vmware.1-tkg.1
  - v1.20.14+vmware.1-tkg.1
- version: v1.4.2
  supportedKubernetesVersions:
  - v1.21.8+vmware.1-tkg.2
  - v1.19.16+vmware.1-tkg.1
  - v1.20.14+vmware.1-tkg.2
- version: v1.4.1
  supportedKubernetesVersions:
  - v1.21.2+vmware.1-tkg.2
  - v1.20.8+vmware.1-tkg.3
  - v1.19.12+vmware.1-tkg.2
- version: v1.3.0
  supportedKubernetesVersions:
  - v1.20.4+vmware.1-tkg.1
  - v1.19.8+vmware.1-tkg.1
  - v1.18.16+vmware.1-tkg.1
  - v1.17.16+vmware.2-tkg.1
- version: v1.3.1
  supportedKubernetesVersions:
  - v1.19.8+vmware.3-tkg.1
  - v1.20.5+vmware.2-tkg.1
  - v1.18.17+vmware.2-tkg.1
  - v1.20.4+vmware.3-tkg.1
  - v1.19.9+vmware.2-tkg.1
  - v1.18.16+vmware.3-tkg.1
  - v1.17.16+vmware.3-tkg.1
- version: v1.3.1-fips.1
  supportedKubernetesVersions:
  - v1.20.5+vmware.2-fips.1-tkg.1
- version: v1.3.1-patch1
  supportedKubernetesVersions:
  - v1.19.8+vmware.3-tkg.1
  - v1.20.5+vmware.2-tkg.1
  - v1.18.17+vmware.2-tkg.1
  - v1.20.4+vmware.3-tkg.1
  - v1.19.9+vmware.2-tkg.1
  - v1.18.16+vmware.3-tkg.1
  - v1.17.16+vmware.3-tkg.1
- version: v1.4.0
  supportedKubernetesVersions:
  - v1.19.12+vmware.1-tkg.1
  - v1.21.2+vmware.1-tkg.1
  - v1.20.8+vmware.1-tkg.2
- version: v1.4.0-fips.1
  supportedKubernetesVersions:
  - v1.21.2+vmware.1-fips.1-tkg.1
  - v1.20.8+vmware.1-fips.1-tkg.2

projects.registry.vmware.com/tkg/tkr-bom:v1.22.5_vmware.1-tkg.3:

$ rg -i 'kapp-controller' -A 3

tkr-bom-v1.22.5+vmware.1-tkg.3.yaml
92:  kapp-controller:
93-  - version: v0.30.0+vmware.1
94-    images:
95-      kappControllerImage:
96:        imagePath: kapp-controller
97-        tag: v0.30.0_vmware.1
98-  kubernetes:
99-  - version: v1.22.5+vmware.1
--
188:      kapp-controller.tanzu.vmware.com:
189:        imagePath: packages/core/kapp-controller
190-        tag: v0.30.0_vmware.1-tkg.1
191-      load-balancer-and-ingress-service.tanzu.vmware.com:
192-        imagePath: packages/core/load-balancer-and-ingress-service
--
459:  kapp-controller:
460-    category: addons-management
461-    clusterTypes:
462-    - management
--
464:    packageName: kapp-controller.tanzu.vmware.com
465-  load-balancer-and-ingress-service:
466-    category: networking
467-    clusterTypes:

@joshrosso joshrosso assigned joshrosso and unassigned joshrosso Mar 1, 2022
@joshrosso
Copy link
Contributor Author

Once we get a build based on TKG 1.5.1, we just need to verify kapp-controller is v0.30.0.

@joshrosso joshrosso self-assigned this Mar 4, 2022
@joshrosso
Copy link
Contributor Author

joshrosso commented Mar 10, 2022 •
edited
Loading

Validated using:

$ tanzu mc version
v0.11.2

cgroups are v2:

$ mount | grep cgroup
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)

BoM is:

$ tree ~/.config/tanzu/tkg/bom/
/home/josh/.config/tanzu/tkg/bom/
├── tkg-bom-v1.5.1-tf-v0.11.2.yaml
└── tkr-bom-v1.22.5+vmware.1-tkg.3-tf-v0.11.2.yaml

Cluster validated against:

$ CLUSTER_PLAN=dev tanzu mc create -i docker hellodog                                                                                                            

Validating the pre-requisites...
Identity Provider not configured. Some authentication features won't work.
WARNING: key is not a string: %!s(int=1)WARNING: key is not a string: %!s(int=1)
Setting up management cluster...
Validating configuration...
Using infrastructure provider docker:v1.0.1
Generating cluster configuration...
WARNING: key is not a string: %!s(int=1)WARNING: key is not a string: %!s(int=1)Setting up bootstrapper...
Bootstrapper created. Kubeconfig: /home/josh/.kube-tkg/tmp/config_WiN6XnLk
Installing providers on bootstrapper...
Fetching providers
Installing cert-manager Version="v1.5.3"
Waiting for cert-manager to be available...
Installing Provider="cluster-api" Version="v1.0.1" TargetNamespace="capi-system"
Installing Provider="bootstrap-kubeadm" Version="v1.0.1" TargetNamespace="capi-kubeadm-bootstrap-system"
Installing Provider="control-plane-kubeadm" Version="v1.0.1" TargetNamespace="capi-kubeadm-control-plane-system"
Installing Provider="infrastructure-docker" Version="v1.0.1" TargetNamespace="capd-system"
Start creating management cluster...
[cluster control plane is still being initialized: WaitingForControlPlane, cluster infrastructure is still being provisioned: WaitingForControlPlane]
cluster control plane is still being initialized: ScalingUp
Saving management cluster kubeconfig into /home/josh/.kube/config
Installing providers on management cluster...
Fetching providers
I0309 17:44:26.676239 1710039 request.go:665] Waited for 1.04832142s due to client-side throttling, not priority and fairness, request: GET:https://172.18.0.3:6443/apis/policy/v1beta1?timeout=30s
Installing cert-manager Version="v1.5.3"
Waiting for cert-manager to be available...
Installing Provider="cluster-api" Version="v1.0.1" TargetNamespace="capi-system"
I0309 17:49:45.279434 1710039 request.go:665] Waited for 1.043001547s due to client-side throttling, not priority and fairness, request: GET:https://172.18.0.3:6443/apis/stats.antrea.io/v1alpha1?timeout=30s
Installing Provider="bootstrap-kubeadm" Version="v1.0.1" TargetNamespace="capi-kubeadm-bootstrap-system"
Installing Provider="control-plane-kubeadm" Version="v1.0.1" TargetNamespace="capi-kubeadm-control-plane-system"
Installing Provider="infrastructure-docker" Version="v1.0.1" TargetNamespace="capd-system"
I0309 17:49:55.327038 1710039 request.go:665] Waited for 1.491146562s due to client-side throttling, not priority and fairness, request: GET:https://172.18.0.3:6443/apis/crd.antrea.io/v1beta1?timeout=30s
Waiting for the management cluster to get ready for move...
Waiting for addons installation...
Moving all Cluster API objects from bootstrap cluster to management cluster...
Performing move...
Discovering Cluster API objects
Moving Cluster API objects Clusters=1
Creating objects in the target cluster
Deleting objects from the source cluster
Waiting for additional components to be up and running...
Waiting for packages to be up and running...
Warning: Management cluster is created successfully, but some packages are failing. Failure while waiting for packages to be installed: package reconciliation failed:
You can now access the management cluster tkg-mgmt-docker-20220309174206 by running 'kubectl config use-context tkg-mgmt-docker-20220309174206-admin@tkg-mgmt-docker-20220309174206'

Management cluster created!


You can now create your first workload cluster by running the following:

  tanzu cluster create [name] -f [file]


Some addons might be getting installed! Check their status by running the following:

  kubectl get apps -A

Checking for required plugins...
All required plugins are already installed and up-to-date

kapp-controller version validated with:

$ docker exec -it bc9c8f747a6c kubectl get po -n tkg-system --kubeconfig=/etc/kubernetes/admin.conf kapp-controller-9dbc57fc6-x2cb7 -oyaml | rg image
    image: projects-stg.registry.vmware.com/tkg/kapp-controller:v0.30.0_vmware.1
    imagePullPolicy: IfNotPresent
    image: projects-stg.registry.vmware.com/tkg/kapp-controller:v0.30.0_vmware.1
    imagePullPolicy: IfNotPresent
    image: projects-stg.registry.vmware.com/tkg/kapp-controller:v0.30.0_vmware.1
    imageID: projects-stg.registry.vmware.com/tkg/kapp-controller@sha256:e4cfadd453f7d452654c6074878ad454d3dbff4e4a9ab537b461fedf46c62672
    image: projects-stg.registry.vmware.com/tkg/kapp-controller:v0.30.0_vmware.1
    imageID: projects-stg.registry.vmware.com/tkg/kapp-controller@sha256:e4cfadd453f7d452654c6074878ad454d3dbff4e4a9ab537b461fedf46c62672

Summary:

TCE v0.11.0 will feature kapp-controller v0.30.0.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@joshrosso joshrosso

Labels
kind/feature A request for a new feature owner/framework Work executed in vmware-tanzu/tanzu-framework owner/packages Work executed by a package's maintainer reporting/health/on-track
Projects
None yet
Milestone
v0.11.0
Development

No branches or pull requests
2 participants
@seemiller @joshrosso