Skip to content

Conversation

mhotan
Copy link
Contributor

@mhotan mhotan commented Oct 15, 2025

Context: We are converging on a world where the Dataplane and
Controlplane will be designed to run their own respective ingress.
This adds a natural separate of concern and allows maximum
configurability between the two services.

  • Update dataplane values.yaml with Union specific controller defaults
  • Don't always assume the Values.host is the ingress host. This allows
    to not couple the two. Leaving Ingress host empty is now feasible and
    less coupling. This also supports a world that allows dataplane to
    interact with controlplane intra-cluster.

Context: We are converging on a world where the Dataplane and
Controlplane will be designed to run their own respective ingress.
This adds a natural separate of concern and allows maximum
configurability between the two services.

* Update dataplane values.yaml with Union specific controller defaults
* Don't always assume the `Values.host` is the ingress host. This allows
  to not couple the two. Leaving Ingress host empty is now feasible and
  less coupling. This also supports a world that allows dataplane to
  interact with controlplane intra-cluster.
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