Skip to content
This repository was archived by the owner on Jun 11, 2025. It is now read-only.

Feat/environments and wireguard#103

Merged
nxtcoder17 merged 5 commits into
release-1.0.5from
feat/environments-and-wireguard
Jan 9, 2024
Merged

Feat/environments and wireguard#103
nxtcoder17 merged 5 commits into
release-1.0.5from
feat/environments-and-wireguard

Conversation

@nxtcoder17
Copy link
Copy Markdown
Member

Description

  • Environments is now available on agents
  • Environment now takes control of routing in it's .spec.targetNamespace.
  • coredns corefile updates for environment level domain routing
  • wireguard operator is now available in agent operator

controllers

- environments will now have their own ingress controllers, which are
  accessible only locally to the cluster.
- Our Wireguard Devices will allow the connection to go through as it is
  happening to a remote url, (https/tls termination is all done by
  ingress itself, as previously in any router)

- this gives us the ability to route same domains to N different
  environments at the same time
- corefile updates for environment level domain routing
- fixes corefile configuration sync, with our custom coredns image
- fixes wireguard device rollouts
@nxtcoder17 nxtcoder17 merged commit 22555ae into release-1.0.5 Jan 9, 2024
@nxtcoder17 nxtcoder17 deleted the feat/environments-and-wireguard branch January 9, 2024 10:50
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant