TMC Self-Managed Upgrade to 1.0.1
Overview
TMC Self-Managed version 1.0.1
Not that long ago I published an article where I went through how to deploy TMC-SM in my lab, the post can be found here. That post were based on the first release of TMC local, version 1.0. Now version 1.0.1 is out and I figured I wanted to create a post how I upgrade my current TMC local installation to the latest version 1.0.1. And who knows, maybe this will be a short and snappy post from me for a change 😄
Whats new in TMC-SM 1.0.1
Taken from the official documentaion page here where you can find more details, like information about issues that have been resolved.
Tanzu Mission Control Self-Managed now supports deployment to and lifecycle management of the following Tanzu Kubernetes Grid clusters:
| Cluster type | Environment |
|---|---|
| TKG 2.2.x (Kubernetes 1.25.x) | vSphere 8.0 and vSphere 7.0 |
| TKG 2.1.x (Kubernetes 1.24.x) | vSphere 8.0 and vSphere 7.0 |
| TKG 1.6.x (Kubernetes 1.23.x) | vSphere 7.0 |
| Tanzu Kubernetes Grid Service clusters running in vSphere with Tanzu (Kubernetes 1.24.x and 1.23.x) | vSphere 8.0 Update 0 or Update 2 vSphere 7.0 latest update |
New Features and Improvements
-
Added lifecycle management support for vSphere 8
You can now manage Tanzu Kubernetes Grid Service clusters running in vSphere with Tanzu 8u1b. Tanzu Mission Control Self-Managed allows you to register your vSphere with Tanzu Supervisor to perform lifecycle management operations on your Tanzu Kubernetes Grid service clusters.
-
Added Terraform provider support for Tanzu Mission Control Self-Managed
Tanzu Mission Control Self-Managed can now be managed and automated using Hashicorp Terraform platform.
The Tanzu Mission Control provider v1.2.1 in Terraform implements support for managing your fleet of Kubernetes clusters by connecting with Tanzu Mission Control Self-Managed.
You can use the Tanzu Mission Control provider for Terraform to:
-
Connect to Tanzu Mission Control Self-Managed.
-
Attach conformant Kubernetes clusters.
-
Manage the lifecycle of workload clusters.
-
Manage cluster security using policies - access, image registry, security, network, custom, namespace quota.
-
Upgrade TMC-SM to 1.0.1
I am using the steps describing how to upgrade TMC-SM in this chapter from the official TMC documentation page here. Before executing the actual upgrade process there are some necessary steps that needs to be done first. I will go through them here in their own little chapters/sections below. I will reuse the same bootstrap machine and container registry I used in this post in all the steps described.
Download the latest packages
First I need to download the latest packages from the VMware Customer Connect portal here. The file I will be downloading is this:
This file will be landing on my laptop where I will copy it over to my bootstrap machine as soon as it is downloaded.
1andreasm:~/Downloads/TMC$ scp bundle-1.0.1.tar andreasm@10.101.10.99:/home/andreasm/tmc-sm
2andreasm@10.101.10.99's password:
3bundle-1.0.1.tar 15% 735MB 5.3MB/s 13:05 ETA
Extract and push images to registry
From my bootstrap machine I need to extract the newly downloaded bundle-1.0.1.tar file, and put it in a new folder:
1andreasm@linuxvm01:~/tmc-sm$ mkdir tmc-sm-1.0.1
2andreasm@linuxvm01:~/tmc-sm$ tar -xf bundle-1.0.1.tar -C ./tmc-sm-1.0.1/
Then I will push them to my registry, the same registry and project used in the first installation of TMC-SM.
1andreasm@linuxvm01:~/tmc-sm/tmc-sm-1.0.1$ ./tmc-sm push-images harbor --project registry.some-domain.net/tmcproject --username username --password password
After some waiting, the below should be the output if everything went successfully.
1INFO[0171] Pushing PackageRepository uri=registry.some-domain.net/tmc-project/package-repository
2Image Staging Complete. Next Steps:
3Setup Kubeconfig (if not already done) to point to cluster:
4export KUBECONFIG={YOUR_KUBECONFIG}
5
6Create 'tmc-local' namespace: kubectl create namespace tmc-local
7
8Download Tanzu CLI from Customer Connect (If not already installed)
9
10Update TMC Self Managed Package Repository:
11Run: tanzu package repository add tanzu-mission-control-packages --url "registry.some-domain.net/tmc-project/package-repository:1.0.1" --namespace tmc-local
12
13Create a values based on the TMC Self Managed Package Schema:
14View the Values Schema: tanzu package available get "tmc.tanzu.vmware.com/1.0.1" --namespace tmc-local --values-schema
15Create a Values file named values.yaml matching the schema
16
17Install the TMC Self Managed Package:
18Run: tanzu package install tanzu-mission-control -p tmc.tanzu.vmware.com --version "1.0.1" --values-file values.yaml --namespace tmc-local
I should also have a file called pushed-package-repository.json in my tmc-sm-1.0.1 folder:
1andreasm@linuxvm01:~/tmc-sm/tmc-sm-1.0.1$ ls
2agent-images dependencies packages pushed-package-repository.json tmc-sm
The content of this file:
1andreasm@linuxvm01:~/tmc-sm/tmc-sm-1.0.1$ cat pushed-package-repository.json
2{"repositoryImage":"registry.some-domain.net/tmc-project/package-repository","version":"1.0.1"}
This information is needed in the next step.
Update tanzu package repository
This step will update the already installed tmc-sm package repository to contain version 1.0.1. Make sure to be logged into the correct context, the kubernetes cluster where the TMC installation is running before doing the below.
1#Using the information above from the pushed-package-repository file, execute the following command:
2tanzu package repository update tanzu-mission-control-packages --url "registry.some-domain.net/tmc-project/package-repository:1.0.1" --namespace tmc-local
1Waiting for package repository to be updated
2
311:10:20AM: Waiting for package repository reconciliation for 'tanzu-mission-control-packages'
411:10:25AM: Waiting for generation 2 to be observed
511:10:29AM: Fetching
6 | apiVersion: vendir.k14s.io/v1alpha1
7 | directories:
8 | - contents:
9 | - imgpkgBundle:
10 | image: registry.some-domain.net/tmc-project/package-repository@sha256:89e53c26a9184580c2778a3bf08c45392e1d09773f0e8d1c22052dfb
11 | tag: 1.0.1
12 | path: .
13 | path: "0"
14 | kind: LockConfig
15 |
1611:10:29AM: Fetch succeeded
1711:10:30AM: Template succeeded
1811:10:30AM: Deploy started (3s ago)
1911:10:33AM: Deploying
20 | Target cluster 'https://20.10.0.1:443'
21 | Changes
22 | Namespace Name Kind Age Op Op st. Wait to Rs Ri
23 | tmc-local contour.bitnami.com.12.1.0 Package 51d delete - - ok -
24 | ^ contour.bitnami.com.12.2.6 Package - create ??? - - -
25 | ^ kafka-topic-controller.tmc.tanzu.vmware.com.0.0.21 Package 51d delete - - ok -
26 | ^ kafka-topic-controller.tmc.tanzu.vmware.com.0.0.22 Package - create ??? - - -
27 | ^ kafka.bitnami.com.22.1.3 Package 51d delete - - ok -
28 | ^ kafka.bitnami.com.23.0.7 Package - create ??? - - -
29 | ^ minio.bitnami.com.12.6.12 Package - create ??? - - -
30 | ^ minio.bitnami.com.12.6.4 Package 51d delete - - ok -
31 | ^ monitoring.tmc.tanzu.vmware.com.0.0.13 Package 51d delete - - ok -
32 | ^ monitoring.tmc.tanzu.vmware.com.0.0.14 Package - create ??? - - -
33 | ^ pinniped.bitnami.com.1.2.1 Package 51d delete - - ok -
34 | ^ pinniped.bitnami.com.1.2.8 Package - create ??? - - -
35 | ^ postgres-endpoint-controller.tmc.tanzu.vmware.com.0.1.43 Package 51d delete - - ok -
36 | ^ postgres-endpoint-controller.tmc.tanzu.vmware.com.0.1.47 Package - create ??? - - -
37 | ^ s3-access-operator.tmc.tanzu.vmware.com.0.1.22 Package 51d delete - - ok -
38 | ^ s3-access-operator.tmc.tanzu.vmware.com.0.1.24 Package - create ??? - - -
39 | ^ tmc-local-postgres.tmc.tanzu.vmware.com.0.0.46 Package 51d delete - - ok -
40 | ^ tmc-local-postgres.tmc.tanzu.vmware.com.0.0.67 Package - create ??? - - -
41 | ^ tmc-local-stack-secrets.tmc.tanzu.vmware.com.0.0.17161 Package 51d delete - - ok -
42 | ^ tmc-local-stack-secrets.tmc.tanzu.vmware.com.0.0.21880 Package - create ??? - - -
43 | ^ tmc-local-stack.tmc.tanzu.vmware.com.0.0.17161 Package 51d delete - - ok -
44 | ^ tmc-local-stack.tmc.tanzu.vmware.com.0.0.21880 Package - create ??? - - -
45 | ^ tmc-local-support.tmc.tanzu.vmware.com.0.0.17161 Package 51d delete - - ok -
46 | ^ tmc-local-support.tmc.tanzu.vmware.com.0.0.21880 Package - create ??? - - -
47 | ^ tmc.tanzu.vmware.com.1.0.0 Package 51d delete - - ok -
48 | ^ tmc.tanzu.vmware.com.1.0.1 Package - create ??? - - -
49 | Op: 13 create, 13 delete, 0 update, 0 noop, 0 exists
50 | Wait to: 0 reconcile, 0 delete, 26 noop
51 | 11:10:32AM: ---- applying 26 changes [0/26 done] ----
52 | 11:10:32AM: delete package/tmc.tanzu.vmware.com.1.0.0 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
53 | 11:10:32AM: delete package/monitoring.tmc.tanzu.vmware.com.0.0.13 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
54 | 11:10:32AM: create package/tmc.tanzu.vmware.com.1.0.1 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
55 | 11:10:32AM: delete package/s3-access-operator.tmc.tanzu.vmware.com.0.1.22 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
56 | 11:10:32AM: delete package/tmc-local-postgres.tmc.tanzu.vmware.com.0.0.46 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
57 | 11:10:32AM: delete package/pinniped.bitnami.com.1.2.1 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
58 | 11:10:32AM: delete package/tmc-local-stack.tmc.tanzu.vmware.com.0.0.17161 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
59 | 11:10:32AM: delete package/tmc-local-stack-secrets.tmc.tanzu.vmware.com.0.0.17161 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
60 | 11:10:32AM: delete package/minio.bitnami.com.12.6.4 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
61 | 11:10:32AM: delete package/tmc-local-support.tmc.tanzu.vmware.com.0.0.17161 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
62 | 11:10:32AM: delete package/contour.bitnami.com.12.1.0 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
63 | 11:10:32AM: delete package/postgres-endpoint-controller.tmc.tanzu.vmware.com.0.1.43 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
64 | 11:10:32AM: delete package/kafka-topic-controller.tmc.tanzu.vmware.com.0.0.21 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
65 | 11:10:32AM: create package/kafka-topic-controller.tmc.tanzu.vmware.com.0.0.22 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
66 | 11:10:32AM: delete package/kafka.bitnami.com.22.1.3 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
67 | 11:10:32AM: create package/minio.bitnami.com.12.6.12 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
68 | 11:10:32AM: create package/pinniped.bitnami.com.1.2.8 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
69 | 11:10:32AM: create package/tmc-local-postgres.tmc.tanzu.vmware.com.0.0.67 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
70 | 11:10:32AM: create package/contour.bitnami.com.12.2.6 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
71 | 11:10:32AM: create package/monitoring.tmc.tanzu.vmware.com.0.0.14 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
72 | 11:10:32AM: create package/postgres-endpoint-controller.tmc.tanzu.vmware.com.0.1.47 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
73 | 11:10:32AM: create package/tmc-local-stack-secrets.tmc.tanzu.vmware.com.0.0.21880 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
74 | 11:10:32AM: create package/tmc-local-stack.tmc.tanzu.vmware.com.0.0.21880 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
75 | 11:10:32AM: create package/s3-access-operator.tmc.tanzu.vmware.com.0.1.24 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
76 | 11:10:32AM: create package/tmc-local-support.tmc.tanzu.vmware.com.0.0.21880 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
77 | 11:10:33AM: create package/kafka.bitnami.com.23.0.7 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
78 | 11:10:33AM: ---- waiting on 26 changes [0/26 done] ----
79 | 11:10:33AM: ok: noop package/kafka.bitnami.com.23.0.7 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
80 | 11:10:33AM: ok: noop package/kafka-topic-controller.tmc.tanzu.vmware.com.0.0.21 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
81 | 11:10:33AM: ok: noop package/monitoring.tmc.tanzu.vmware.com.0.0.13 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
82 | 11:10:33AM: ok: noop package/tmc.tanzu.vmware.com.1.0.1 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
83 | 11:10:33AM: ok: noop package/s3-access-operator.tmc.tanzu.vmware.com.0.1.22 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
84 | 11:10:33AM: ok: noop package/tmc-local-postgres.tmc.tanzu.vmware.com.0.0.46 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
85 | 11:10:33AM: ok: noop package/pinniped.bitnami.com.1.2.1 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
86 | 11:10:33AM: ok: noop package/tmc-local-stack.tmc.tanzu.vmware.com.0.0.17161 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
87 | 11:10:33AM: ok: noop package/tmc-local-stack-secrets.tmc.tanzu.vmware.com.0.0.17161 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
88 | 11:10:33AM: ok: noop package/minio.bitnami.com.12.6.4 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
89 | 11:10:33AM: ok: noop package/tmc-local-support.tmc.tanzu.vmware.com.0.0.17161 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
90 | 11:10:33AM: ok: noop package/contour.bitnami.com.12.1.0 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
91 | 11:10:33AM: ok: noop package/postgres-endpoint-controller.tmc.tanzu.vmware.com.0.1.43 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
92 | 11:10:33AM: ok: noop package/contour.bitnami.com.12.2.6 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
93 | 11:10:33AM: ok: noop package/kafka-topic-controller.tmc.tanzu.vmware.com.0.0.22 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
94 | 11:10:33AM: ok: noop package/kafka.bitnami.com.22.1.3 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
95 | 11:10:33AM: ok: noop package/minio.bitnami.com.12.6.12 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
96 | 11:10:33AM: ok: noop package/pinniped.bitnami.com.1.2.8 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
97 | 11:10:33AM: ok: noop package/tmc-local-postgres.tmc.tanzu.vmware.com.0.0.67 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
98 | 11:10:33AM: ok: noop package/tmc-local-stack-secrets.tmc.tanzu.vmware.com.0.0.21880 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
99 | 11:10:33AM: ok: noop package/monitoring.tmc.tanzu.vmware.com.0.0.14 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
100 | 11:10:33AM: ok: noop package/postgres-endpoint-controller.tmc.tanzu.vmware.com.0.1.47 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
101 | 11:10:33AM: ok: noop package/s3-access-operator.tmc.tanzu.vmware.com.0.1.24 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
102 | 11:10:33AM: ok: noop package/tmc-local-stack.tmc.tanzu.vmware.com.0.0.21880 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
103 | 11:10:33AM: ok: noop package/tmc-local-support.tmc.tanzu.vmware.com.0.0.21880 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
104 | 11:10:33AM: ok: noop package/tmc.tanzu.vmware.com.1.0.0 (data.packaging.carvel.dev/v1alpha1) namespace: tmc-local
105 | 11:10:33AM: ---- applying complete [26/26 done] ----
106 | 11:10:33AM: ---- waiting complete [26/26 done] ----
107 | Succeeded
10811:10:33AM: Deploy succeeded
If everything went well, lets check the package version:
1andreasm@linuxvm01:~/tanzu package repository list --namespace tmc-local
2
3 NAME SOURCE STATUS
4 tanzu-mission-control-packages (imgpkg) registry.some-domain.net/tmc-project/package-repository:1.0.1 Reconcile succeeded
After the steps above, we are now ready to start the actual upgrade of the TMC-SM deployment.
Upgrade TMC-SM deployment
To upgrade TMC execute the below command, where values.yaml is the value.yaml file I used in the previous installation:
1andreasm@linuxvm01:~/tanzu package installed update tanzu-mission-control -p tmc.tanzu.vmware.com --version "1.0.1" --values-file values.yaml --namespace tmc-local
Now some output:
111:19:14AM: Pausing reconciliation for package installation 'tanzu-mission-control' in namespace 'tmc-local'
211:19:15AM: Updating secret 'tanzu-mission-control-tmc-local-values'
311:19:15AM: Creating overlay secrets
411:19:15AM: Updating package install for 'tanzu-mission-control' in namespace 'tmc-local'
511:19:15AM: Resuming reconciliation for package installation 'tanzu-mission-control' in namespace 'tmc-local'
611:19:15AM: Waiting for PackageInstall reconciliation for 'tanzu-mission-control'
711:19:15AM: Waiting for generation 9 to be observed
811:19:15AM: ReconcileFailed: kapp: Error: waiting on reconcile packageinstall/kafka-topic-controller (packaging.carvel.dev/v1alpha1) namespace: tmc-local:
9 Finished unsuccessfully (Reconcile failed: (message: Expected to find at least one version, but did not (details: all=1 -> after-prereleases-filter=1 -> after-kapp-controller-version-check=1 -> after-constraints-filter=0)))
1011:19:15AM: Error tailing app: Reconciling app: ReconcileFailed: kapp: Error: waiting on reconcile packageinstall/kafka-topic-controller (packaging.carvel.dev/v1alpha1) namespace: tmc-local:
11 Finished unsuccessfully (Reconcile failed: (message: Expected to find at least one version, but did not (details: all=1 -> after-prereleases-filter=1 -> after-kapp-controller-version-check=1 -> after-constraints-filter=0)))
12
1311:19:16AM: packageinstall/tanzu-mission-control (packaging.carvel.dev/v1alpha1) namespace: tmc-local: Reconciling
1411:19:46AM: packageinstall/tanzu-mission-control (packaging.carvel.dev/v1alpha1) namespace: tmc-local: Reconciling
1511:20:17AM: packageinstall/tanzu-mission-control (packaging.carvel.dev/v1alpha1) namespace: tmc-local: Reconciling
1611:20:47AM: packageinstall/tanzu-mission-control (packaging.carvel.dev/v1alpha1) namespace: tmc-local: Reconciling
1711:21:17AM: packageinstall/tanzu-mission-control (packaging.carvel.dev/v1alpha1) namespace: tmc-local: Reconciling
1811:21:48AM: packageinstall/tanzu-mission-control (packaging.carvel.dev/v1alpha1) namespace: tmc-local: Reconciling
1911:22:19AM: packageinstall/tanzu-mission-control (packaging.carvel.dev/v1alpha1) namespace: tmc-local: Reconciling
2011:22:49AM: packageinstall/tanzu-mission-control (packaging.carvel.dev/v1alpha1) namespace: tmc-local: Reconciling
2111:23:19AM: packageinstall/tanzu-mission-control (packaging.carvel.dev/v1alpha1) namespace: tmc-local: Reconciling
2211:23:49AM: packageinstall/tanzu-mission-control (packaging.carvel.dev/v1alpha1) namespace: tmc-local: Reconciling
2311:24:19AM: packageinstall/tanzu-mission-control (packaging.carvel.dev/v1alpha1) namespace: tmc-local: Reconciling
2411:24:49AM: packageinstall/tanzu-mission-control (packaging.carvel.dev/v1alpha1) namespace: tmc-local: Reconciling
2511:25:20AM: packageinstall/tanzu-mission-control (packaging.carvel.dev/v1alpha1) namespace: tmc-local: Reconciling
2611:25:50AM: packageinstall/tanzu-mission-control (packaging.carvel.dev/v1alpha1) namespace: tmc-local: Reconciling
2711:26:20AM: packageinstall/tanzu-mission-control (packaging.carvel.dev/v1alpha1) namespace: tmc-local: Reconciling
2811:26:51AM: packageinstall/tanzu-mission-control (packaging.carvel.dev/v1alpha1) namespace: tmc-local: Reconciling
2911:27:22AM: packageinstall/tanzu-mission-control (packaging.carvel.dev/v1alpha1) namespace: tmc-local: Reconciling
3011:27:49AM: packageinstall/tanzu-mission-control (packaging.carvel.dev/v1alpha1) namespace: tmc-local: ReconcileSucceeded
I did experience some error issues like the ones above Error tailing app: Reconciling app: ReconcileFailed: kapp: Error: waiting on reconcile, (Reconcile failed: (message: Expected to find at least one version, but did not
I monitored the progress with this command:
1kubectl get pkgi -n tmc-local
Which first gave me this:
1NAME PACKAGE NAME PACKAGE VERSION DESCRIPTION AGE
2contour contour.bitnami.com 12.2.6 Reconciling 51d
3kafka kafka.bitnami.com 22.1.3 Reconcile failed: Expected to find at least one version, but did not (details: a... 51d
4kafka-topic-controller kafka-topic-controller.tmc.tanzu.vmware.com 0.0.21 Reconcile failed: Expected to find at least one version, but did not (details: a... 51d
5minio minio.bitnami.com 12.6.4 Reconcile failed: Expected to find at least one version, but did not (details: a... 51d
6pinniped pinniped.bitnami.com 1.2.1 Reconcile failed: Expected to find at least one version, but did not (details: a... 51d
7postgres tmc-local-postgres.tmc.tanzu.vmware.com 0.0.46 Reconcile failed: Expected to find at least one version, but did not (details: a... 51d
8postgres-endpoint-controller postgres-endpoint-controller.tmc.tanzu.vmware.com 0.1.43 Reconcile failed: Expected to find at least one version, but did not (details: a... 51d
9s3-access-operator s3-access-operator.tmc.tanzu.vmware.com 0.1.22 Reconcile failed: Expected to find at least one version, but did not (details: a... 51d
10tanzu-mission-control tmc.tanzu.vmware.com 1.0.1 Reconciling 51d
11tmc-local-monitoring monitoring.tmc.tanzu.vmware.com 0.0.13 Reconcile failed: Expected to find at least one version, but did not (details: a... 51d
12tmc-local-stack tmc-local-stack.tmc.tanzu.vmware.com 0.0.17161 Reconcile failed: Expected to find at least one version, but did not (details: a... 51d
13tmc-local-stack-secrets tmc-local-stack-secrets.tmc.tanzu.vmware.com 0.0.21880 Reconcile succeeded 51d
14tmc-local-support tmc-local-support.tmc.tanzu.vmware.com 0.0.17161 Reconcile failed: Expected to find at least one version, but did not (details: a... 51d
But after a little while I tried it again and now it looked much better:
1NAME PACKAGE NAME PACKAGE VERSION DESCRIPTION AGE
2contour contour.bitnami.com 12.2.6 Reconcile succeeded 51d
3kafka kafka.bitnami.com 23.0.7 Reconcile succeeded 51d
4kafka-topic-controller kafka-topic-controller.tmc.tanzu.vmware.com 0.0.22 Reconcile succeeded 51d
5minio minio.bitnami.com 12.6.12 Reconcile succeeded 51d
6pinniped pinniped.bitnami.com 1.2.8 Reconcile succeeded 51d
7postgres tmc-local-postgres.tmc.tanzu.vmware.com 0.0.67 Reconcile succeeded 51d
8postgres-endpoint-controller postgres-endpoint-controller.tmc.tanzu.vmware.com 0.1.47 Reconcile succeeded 51d
9s3-access-operator s3-access-operator.tmc.tanzu.vmware.com 0.1.24 Reconcile succeeded 51d
10tanzu-mission-control tmc.tanzu.vmware.com 1.0.1 Reconciling 51d
11tmc-local-monitoring monitoring.tmc.tanzu.vmware.com 0.0.14 Reconciling 51d
12tmc-local-stack tmc-local-stack.tmc.tanzu.vmware.com 0.0.21880 Reconcile succeeded 51d
13tmc-local-stack-secrets tmc-local-stack-secrets.tmc.tanzu.vmware.com 0.0.21880 Reconcile succeeded 51d
14tmc-local-support tmc-local-support.tmc.tanzu.vmware.com 0.0.21880 Reconcile succeeded 51d
And if I look at the pods for the deployment:
1NAME READY STATUS RESTARTS AGE
2account-manager-server-dd4cb648-mhwsr 1/1 Running 2 (8m35s ago) 51d
3account-manager-server-dd4cb648-s6n52 1/1 Running 2 (8m34s ago) 51d
4agent-gateway-server-ffbd987f9-79p4v 1/1 Running 0 7m48s
5agent-gateway-server-ffbd987f9-7ggg4 1/1 Running 0 7m48s
6alertmanager-tmc-local-monitoring-tmc-local-0 2/2 Running 0 51d
7api-gateway-server-6ccff88f7c-5wjm7 1/1 Running 0 7m48s
8api-gateway-server-6ccff88f7c-c6srd 1/1 Running 0 7m48s
9audit-service-consumer-6665d4968-mq5k7 1/1 Running 0 7m52s
10audit-service-consumer-6665d4968-nbmcp 1/1 Running 0 7m52s
11audit-service-server-58f8cb48b-cwjd2 1/1 Running 0 7m51s
12audit-service-server-58f8cb48b-drgjq 1/1 Running 0 7m51s
13auth-manager-server-777cff744d-9whfl 1/1 Running 1 (51d ago) 51d
14auth-manager-server-777cff744d-hbqrl 1/1 Running 1 (51d ago) 51d
15auth-manager-server-777cff744d-xxq4w 1/1 Running 2 (51d ago) 51d
16authentication-server-555cd5b896-k7lb7 1/1 Running 0 51d
17authentication-server-555cd5b896-nvhtm 1/1 Running 0 51d
18cluster-agent-service-server-596cdb5968-5dnjz 1/1 Running 0 51d
19cluster-agent-service-server-596cdb5968-p2629 1/1 Running 0 51d
20cluster-config-server-7b5c95f48b-rsvv8 1/1 Running 2 (51d ago) 51d
21cluster-config-server-7b5c95f48b-t89bm 1/1 Running 2 (51d ago) 51d
22cluster-object-service-server-844fc87799-9jjcp 1/1 Running 0 51d
23cluster-object-service-server-844fc87799-mkvvv 1/1 Running 0 51d
24cluster-reaper-server-68b94fdcc6-l4nk4 1/1 Running 0 51d
25cluster-secret-server-6cdc68c88c-2ntj2 1/1 Running 1 (51d ago) 51d
26cluster-secret-server-6cdc68c88c-7vld7 1/1 Running 1 (51d ago) 51d
27cluster-service-server-76d9cc4845-mbmxj 1/1 Running 0 7m51s
28cluster-service-server-76d9cc4845-tl6dg 1/1 Running 0 7m51s
29cluster-sync-egest-5946d85c48-5zzfh 1/1 Running 0 51d
30cluster-sync-egest-5946d85c48-jstjl 1/1 Running 0 51d
31cluster-sync-ingest-b8b4b4f7b-b7t2t 1/1 Running 0 51d
32cluster-sync-ingest-b8b4b4f7b-vjrr7 1/1 Running 0 51d
33contour-contour-certgen-9nhxm 0/1 Completed 0 13m
34contour-contour-f99f8c554-hhl45 1/1 Running 0 13m
35contour-envoy-dkgmp 2/2 Running 0 12m
36contour-envoy-knpcp 2/2 Running 0 13m
37contour-envoy-mdw4l 2/2 Running 0 11m
38contour-envoy-w4wl6 2/2 Running 0 10m
39dataprotection-server-7bd8f57c9c-2b6vc 1/1 Running 0 7m51s
40dataprotection-server-7bd8f57c9c-bxzt2 1/1 Running 0 7m51s
41events-service-consumer-75d7bfbc4f-dkdgt 1/1 Running 0 51d
42events-service-consumer-75d7bfbc4f-hmc4c 1/1 Running 0 51d
43events-service-server-57cb555cc6-6tc27 1/1 Running 0 51d
44events-service-server-57cb555cc6-7jp92 1/1 Running 0 51d
45fanout-service-server-5d854fdcb9-shmsm 1/1 Running 0 51d
46fanout-service-server-5d854fdcb9-z4wb9 1/1 Running 0 51d
47feature-flag-service-server-58cb8b8967-bw8nw 1/1 Running 0 7m49s
48inspection-server-84fbb9f554-8kjll 2/2 Running 0 51d
49inspection-server-84fbb9f554-b4kwq 2/2 Running 0 51d
50intent-server-79db6f6cc8-5bb64 1/1 Running 0 51d
51intent-server-79db6f6cc8-wq46l 1/1 Running 0 51d
52kafka-0 1/1 Running 0 9m37s
53kafka-exporter-f665b6bc5-g6bfg 1/1 Running 4 (8m13s ago) 9m40s
54kafka-topic-controller-7745b56c4c-jxfbv 1/1 Running 0 9m57s
55landing-service-server-86987d87b9-rgxtj 1/1 Running 0 7m49s
56minio-676cfff6d6-pk5m4 1/1 Running 0 8m50s
57minio-provisioning-4wx4j 0/1 Completed 0 8m52s
58onboarding-service-server-7dfd944785-6p4qs 1/1 Running 0 7m49s
59onboarding-service-server-7dfd944785-fknhq 1/1 Running 0 7m49s
60package-deployment-server-5446696ff4-l4phd 1/1 Running 0 51d
61package-deployment-server-5446696ff4-w8sl4 1/1 Running 0 51d
62pinniped-supervisor-f44756bc7-bwtz6 1/1 Running 0 10m
63policy-engine-server-6455f7db8f-748mk 1/1 Running 0 51d
64policy-engine-server-6455f7db8f-pnpr8 1/1 Running 0 51d
65policy-insights-server-6cc68b7d7f-5w9c6 1/1 Running 2 (51d ago) 51d
66policy-sync-service-server-8687654cc9-q98bm 1/1 Running 0 7m49s
67policy-view-service-server-7659f84d-qxdkc 1/1 Running 0 51d
68policy-view-service-server-7659f84d-v95w4 1/1 Running 0 51d
69postgres-endpoint-controller-99987dc75-s2xzv 1/1 Running 0 9m15s
70postgres-postgresql-0 2/2 Running 0 9m32s
71prometheus-server-tmc-local-monitoring-tmc-local-0 2/2 Running 0 6m
72provisioner-service-server-85fb5dc6bc-7n7jh 1/1 Running 0 51d
73provisioner-service-server-85fb5dc6bc-lw8pm 1/1 Running 0 51d
74resource-manager-server-5d69d9fd88-5q97d 1/1 Running 0 7m52s
75resource-manager-server-5d69d9fd88-fw75m 1/1 Running 0 7m52s
76s3-access-operator-7ddb9d9695-l5nx4 1/1 Running 0 9m8s
77schema-service-schema-server-7cc9696fc5-mmv5t 1/1 Running 0 7m51s
78telemetry-event-service-consumer-699db98fc7-kfpht 1/1 Running 0 51d
79telemetry-event-service-consumer-699db98fc7-pg2xg 1/1 Running 0 51d
80tenancy-service-server-6db748f79-pqfzx 1/1 Running 0 7m48s
81ui-server-75ccd455b8-55tkg 1/1 Running 0 7m50s
82ui-server-75ccd455b8-nzw6f 1/1 Running 0 7m50s
83wcm-server-6b4f9c6-c6944 1/1 Running 0 7m51s
84wcm-server-6b4f9c6-wbdm9 1/1 Running 0 7m51s
It looks good, all pods in a running or completed state. Now the logging into the UI:
Thats it. This concludes this post of how to upgrade TMC Self-Managed