Skip to content

Conversation

@c-kruse
Copy link

@c-kruse c-kruse commented Nov 21, 2024

This is what I've had for myself so far!

My workflow to set this is up is:

  1. create three namesapces - mentally assign them a, b or c
  2. for each namesapce kubectl apply -n <namespace> -f ./resources-<a||b||c>/ -f ./listeners-all.yaml
  3. Link sites using CLI.

@c-kruse c-kruse requested review from ajssmith and ssorj November 21, 2024 20:23
@ajssmith
Copy link
Member

Suggest rather than setting up listeners in all sites would be to selectively setup listeners based on what is required by the deployment in the namespace similar to the granularity of the connector definitions.

@c-kruse c-kruse marked this pull request as ready for review February 10, 2025 20:41
resources describing the application network.
commands:
grpc-a:
- run: kubectl create namespace grpc-a
Copy link
Author

Choose a reason for hiding this comment

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

@ssorj this was awkward. I think in v1 skewer there was magic in a standard step to create namespaces based on the sites section.

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