Error on Adding Kubernetes Provider V2 Account

[rajaps369]

I was able to add Kubernetes provider V2. When I gave hal deply apply, I received the following error.

Can anyone help me out here?

bash-5.0$ hal config provider kubernetes account list

• Get current deployment Success

• Get the kubernetes provider Success Validation in default.provider.kubernetes.my-k8s-account:

• WARNING requiredGroupMembership has been deprecated. Please consider moving to using permissions with the flags --read-permissions and --write-permissions instead. Read more at https://spinnaker.io/setup/security/authorization.

• Accounts for kubernetes:

  • default
  • my-k8s-account

bash-5.0$ hal deploy apply

• Get current deployment Success
• Prep deployment Success Validation in default.provider.kubernetes.my-k8s-account:
• WARNING requiredGroupMembership has been deprecated. Please consider moving to using permissions with the flags --read-permissions and --write-permissions instead. Read more at https://spinnaker.io/setup/security/authorization.

Validation in default.stats:

• INFO Stats are currently ENABLED. Usage statistics are being collected. Thank you! These stats inform improvements to the product, and that helps the community. To disable, run hal config stats disable. To learn more about what and how stats data is used, please see https://spinnaker.io/docs/community/stay-informed/stats.

• Preparation complete... deploying Spinnaker

• Get current deployment Success

• Apply deployment Failure

• Deploy spin-clouddriver Failure

• Deploy spin-front50 Failure

• Deploy spin-orca Failure

• Deploy spin-deck Failure

• Deploy spin-echo Failure

• Deploy spin-gate Failure

• Deploy spin-igor Failure

• Deploy spin-rosco Failure Validation in Global: ! ERROR Failed check for Namespace/spinnaker in null Unable to connect to the server: getting credentials: exec: exec: "oci": executable file not found in $PATH

• Failed to deploy Spinnaker.

[rajaps369]

does this required all the these parameters in spinnaker to add multi kubernets provider V2 account.?

hal config provider kubernetes account add my-k8s-account \ --provider-version v2 \ --context context-XXXXX \ --kubeconfig-file /home/spinnaker/.kube/config \ --namespaces "default,spinnaker" \ --only-spinnaker-managed=false \ --required-group-membership="" \ --allowed-accounts "" \ --user-overrides "{'serviceAccount':'dst-account'}" \ --namespace spinnaker \ --configure-image-pulling-secrets=true \ --image-pulling-secret-name XXXXXXX \ --debug

[spinnakerbot]

This issue hasn't been updated in 45 days, so we are tagging it as 'stale'. If you want to remove this label, comment:

@spinnakerbot remove-label stale

[spinnakerbot]

This issue is tagged as 'stale' and hasn't been updated in 45 days, so we are tagging it as 'to-be-closed'. It will be closed in 45 days unless updates are made. If you want to remove this label, comment:

@spinnakerbot remove-label to-be-closed

[spinnakerbot]

This issue is tagged as 'to-be-closed' and hasn't been updated in 45 days, so we are closing it. You can always reopen this issue if needed.

[matheushslage]

Any solution for this? I've been having the same problem using OKE, simply the oci executable is not found. I'm using Ubuntu 22.04. Thanks

[matheushslage]

Any solution for this? I've been having the same problem using OKE, simply the oci executable is not found. I'm using Ubuntu 22.04. Thanks

Kubernetes Service Account works for me. I had a problem generating the token/secret in Kubernetes, it is no longer automatic from version 1.24, so I generated the secret manually and linked it with the service account.