Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installing TAP on Linux Ubuntu - Error deploying secretgen-controller #2187

Open
svianrio opened this issue Aug 8, 2022 · 1 comment
Open
Labels
feedback General feedback

Comments

@svianrio
Copy link

svianrio commented Aug 8, 2022

What content are you providing feedback for?
Installing TAP on Linux Ubuntu - Error deploying secretgen-controller

I need help to install TAP on a Linux box. Got an error deploying secretgen-controller:

Creating namespace tanzu-cluster-essentials

namespace/tanzu-cluster-essentials unchanged

Pulling bundle from registry.tanzu.vmware.com (username: [email protected])

Pulling bundle 'registry.tanzu.vmware.com/tanzu-cluster-essentials/cluster-essentials-bundle@sha256:ab0a3539da241a6ea59c75c0743e9058511d7c56312ea3906178ec0f3491f51d'
Extracting layer 'sha256:2f5a9348c12816475867f535bb6504d3c6f22de2aeaa6ed2e846e560e6b40ac8' (1/1)

Locating image lock file images...
The bundle repo (registry.tanzu.vmware.com/tanzu-cluster-essentials/cluster-essentials-bundle) is hosting every image specified in the bundle's Images Lock file (.imgpkg/images.yml)

Succeeded

Deploying kapp-controller

Target cluster 'https://192.168.49.2:8443' (nodes: minikube)
resolve | final: ghcr.io/vmware-tanzu/carvel-kapp-controller@sha256:d05863e678ea384a55f1315e322c0a8d2f80b571c3418d807921e0eb4cb498ff -> registry.tanzu.vmware.com/tanzu-cluster-essentials/cluster-essentials-bundle@sha256:f1fa5d6ec3a3328f24ad7205d1a6756a022e3c28c129079ec8c012ab6017f286

Changes

Namespace Name Kind Age Op Op st. Wait to Rs Ri

Op: 0 create, 0 delete, 0 update, 0 noop, 0 exists
Wait to: 0 reconcile, 0 delete, 0 noop

Succeeded

Deploying secretgen-controller

ytt: Error: Overlaying data values (in following order: values.yaml, values.yml, additional data values):
One or more data values were invalid

Given data value is not declared in schema
values.yml:
|
4 | registry:
|

= found: registry
= expected: a map item with the key named "secretgenController" (from schema.yaml:5)

Target cluster 'https://192.168.49.2:8443' (nodes: minikube)

kapp: Error: Trying to apply empty set of resources will result in deletion of resources on cluster. Refusing to continue unless --dangerous-allow-empty-list-of-resources is specified.
If this content fell short of your expectations, let us know what you had hoped would be included

Can you help me?

I'm very excited to try TAP. Thanks in advance for your help.

Thanks!

Sergio

@svianrio svianrio added the feedback General feedback label Aug 8, 2022
@benwilcock
Copy link
Contributor

Hey svianrio,

Thanks for getting in touch and for your interest in TAP! Unfortunately for you (and us), installing Tanzu Application Platform locally can give the occasional unexpected problem like this one, but we'll try and help you get through it.

Assuming your PC has the horsepower, the first things to check are the versions of everything. We tested this install against the following for Ubuntu:

  • Ubuntu 20.04 LTS
  • Minikube 1.25 (Docker driver)
  • Kubernetes 1.22.8
  • Kubectl 1.23
  • Tanzu CLI 0.11.2
  • tanzu-cluster-essentials-linux-amd64-1.1.0.tgz

Next is that the right ENV variables have been set in the shell environment you're using for the installation. If you call env there, you should have all the following settings in place for YTT to be able to make the necessary substitutions:

export INSTALL_BUNDLE="registry.tanzu.vmware.com/tanzu-cluster-essentials/cluster-essentials-bundle@sha256:ab0a3539da241a6ea59c75c0743e9058511d7c56312ea3906178ec0f3491f51d"
export INSTALL_REGISTRY_HOSTNAME="registry.tanzu.vmware.com"
export INSTALL_REGISTRY_USERNAME='' # <- Insert Your Tanzu Network username
export INSTALL_REGISTRY_PASSWORD='' # <- Insert Your Tanzu Network password

I would check all these are in place and then follow the instructions again after deleting your Minikube cluster (minikube delete) or using a different minikube profile (more fiddly). Sometimes persistence works and the system can be helped along by a simple retry.

Let us know how you get on.

Cheers,

Ben

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feedback General feedback
Projects
None yet
Development

No branches or pull requests

3 participants
@benwilcock @svianrio and others