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

[chart] Edit NOTES to use more compatible command #612

Merged
merged 3 commits into from
Sep 12, 2018

Conversation

andresmgot
Copy link
Contributor

Fixes https://kubernetes.slack.com/archives/C9D3TSUG4/p1536328485000100

kubectl port-forward to a service is only available with kubectl +1.11. Use the previous approach to ensure that users won't see an error when trying those commands.

@andresmgot andresmgot changed the title [chart] Edit NOTES to use more extended command [chart] Edit NOTES to use more compatible command Sep 11, 2018
@@ -41,7 +41,8 @@ To access Kubeapps from outside your K8s cluster, follow the steps below:
{{- else if contains "ClusterIP" .Values.frontend.service.type }}

echo "Kubeapps URL: http://127.0.0.1:8080"
kubectl port-forward --namespace {{ .Release.Namespace }} svc/{{ template "kubeapps.fullname" . }} 8080:{{ .Values.frontend.service.port }}
export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "app={{ template "kubeapps.fullname" . }}" -o jsonpath="{.items[0].metadata.name}")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

-o name instead of the jsonpath, and tested working on kubectl v1.8.0

@andresmgot andresmgot merged commit bf27e31 into vmware-tanzu:master Sep 12, 2018
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.

2 participants