meshery/meshery
[mesheryctl] Helm: cannot start Meshery: rendered manifests contain a resource that already exists.
Aperta
#4777 aperta il 16 dic 2021
component/mesheryctlhelp wantedissue/willfixkind/buglanguage/go
Metriche repository
- Star
- (10.013 stelle)
- Metriche merge PR
- (Merge medio 22g 16h) (332 PR mergiate in 30 g)
Descrizione
See mesheryctl Command Tracker for current status of commands.
Current Behavior
As a contributor, I have built Meshery Server locally. Meshery Server connects to my Kubernetes cluster and deploys Meshery Operator using helm.
When I cancel the locally-running Meshery Server process, the Meshery Operator deployment stays residual on my Kubernetes cluster.
Then, when I use mesheryctl system start to start Meshery as a user would, I receive the error shown in the logs below.
Desired Behavior
mesheryctl system start should have idempotent behavior in terms of installing Meshery Operator upon connecting to a Kubernetes cluster.
Screenshots/Logs
$ mesheryctl system start
Starting Meshery...
⣯ Deploying Meshery on Kubernetes Error: failed to start Meshery
See https://docs.meshery.io/reference/mesheryctl/system for usage details
: cannot start Meshery: rendered manifests contain a resource that already exists. Unable to continue with install: ServiceAccount "meshery-operator" in namespace "meshery" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "meshery": current value is "meshery-operator"
Environment
- Host OS: Mac
- Meshery Server Version: edge
- Meshery Client Version: stable-v0.6.0-rc-2
- Platform: Kubernetes