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

provider: AKASH_CLUSTER_PUBLIC_HOSTNAME is not used #86

Merged

Conversation

andy108369
Copy link
Collaborator

We set AKASH_CLUSTER_PUBLIC_HOSTNAME to provider.{{ .Values.domain }},
which points to the IP of a woker node where it does not respond over
6443/tcp (kube-apiserver).

As well we are setting AKASH_CLUSTER_K8S=true which makes
AKASH_CLUSTER_PUBLIC_HOSTNAME redundant.

We set AKASH_CLUSTER_PUBLIC_HOSTNAME to `provider.{{ .Values.domain }}`,
which points to the IP of a woker node where it does not respond over
6443/tcp (kube-apiserver).

As well we are setting AKASH_CLUSTER_K8S=true which makes
AKASH_CLUSTER_PUBLIC_HOSTNAME redundant.
@andy108369 andy108369 merged commit a1a5f2a into akash-network:main Jul 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant