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

Update instructions around exposing from a different ns #159

Open
pwright opened this issue May 15, 2023 · 2 comments
Open

Update instructions around exposing from a different ns #159

pwright opened this issue May 15, 2023 · 2 comments

Comments

@pwright
Copy link
Member

pwright commented May 15, 2023

ATM, there's https://skupper.io/docs/cli/index.html#exposing-services-from-different-ns
However, there are now options to :

  • use --enable-cluster-permissions in skupper init

  • and --target-namespace in skupper expose

This feature allows Skupper to monitor deployments in other namespaces

Add doc for these options

NOTE seems to work without --enable-cluster-permissions

  skupper init
  kubectl create namespace east
  kubectl create deployment backend --image quay.io/skupper/hello-world-backend --replicas 3 --namespace east
  skupper expose deployment/backend --port 8080 --target-namespace east
  skupper service status
  kubectl create deployment frontend --image quay.io/skupper/hello-world-frontend
  kubectl expose deployment frontend --port 8080 --type LoadBalancer
  kubectl get service/frontend

@pwright
Copy link
Member Author

pwright commented May 15, 2023

@grs Should we replace existing doc above? or add an optional extra procedure?

Also, does user need extra privs to --enable-cluster-permissions (eg cluster-admin)

@grs
Copy link
Member

grs commented May 15, 2023

Yes, --enable-cluster-permissions requires cluster level privileges. I think we should expand the section to show both targeting a service and a set of pods (e.g. deployment) and explain the differences between the two.

@pwright pwright mentioned this issue Jun 7, 2023
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

No branches or pull requests

2 participants