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

Warning "coalesce.go:199: warning" at a time of installing ztka chart #21

Open
akshay196-rafay opened this issue May 18, 2022 · 1 comment
Assignees
Labels
triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@akshay196-rafay
Copy link
Contributor

akshay196-rafay commented May 18, 2022

The following warnings showing while installing or upgrading ztka chart.

coalesce.go:199: warning: cannot overwrite table with non table for extraInitContainers (map[])
coalesce.go:199: warning: cannot overwrite table with non table for extraContainers (map[])
coalesce.go:199: warning: cannot overwrite table with non table for extraInitContainers (map[])
coalesce.go:199: warning: cannot overwrite table with non table for extraContainers (map[])
coalesce.go:199: warning: cannot overwrite table with non table for extraInitContainers (map[])
coalesce.go:199: warning: cannot overwrite table with non table for extraContainers (map[])

See how to get rid of these warning.

@akshay196-rafay akshay196-rafay self-assigned this May 18, 2022
@akshay196 akshay196 changed the title Warning "coalesce.go:199: warning" at a time of installing rcloud chart Warning "coalesce.go:199: warning" at a time of installing ztka chart Jun 15, 2022
@akshay196 akshay196 added the triage/accepted Indicates an issue or PR is ready to be actively worked on. label Mar 30, 2023
@akshay196
Copy link
Member

Latest chart is not showing these warning messages.

$ helm install myrelease charts/ztka/
NAME: myrelease
LAST DEPLOYED: Sat Apr  1 23:50:54 2023
NAMESPACE: default
STATUS: deployed
REVISION: 1
NOTES:
1. Access the application URL by running these commands:
  Get the EXTERNAL-IP value using following command:
  kubectl get service myrelease-contour-envoy -n default

  Add DNS records of following domains such that it resolves to above <EXTERNAL-IP> value:
  - console.paralus.local
  - *.core-connector.paralus.local
  - *.user.paralus.local

  Open http://console.paralus.local in browser.

  Note: If you are using a cluster with no load-balancer, then the address will be "<pending>".
        If it is Kind or Minikube cluster, check out respective docs to get the external address.

You can view the recovery link for admin user by running the following command once all the pods are running:

kubectl logs -f --namespace default $(kubectl get pods --namespace default -l app.kubernetes.io/name='paralus' -o jsonpath='{ .items[0].metadata.name }') initialize | grep 'Org Admin default password:'

@niravparikh05 @techmaharaj Can you please confirm if this is fixed on your side? We can close this if anyone of you confirms.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

2 participants