With a focus on improving your experience with Helm Charts and introducing Validation Plugins, Monokle Desktop 2.3 is here!
![Monokle Desktop 2.3 Release Notes](https://programming.dev/pictrs/image/75c333ac-441c-4333-ab8e-3f81feab5a71.png?format=webp&thumbnail=256)
Highlights This is the first General Availability (GA) release of Flux v2. Flux v2.0.0 comes with the promotion of the GitOps related APIs to v1 and adds horizontal scaling & sharding capabilities ...
![Release v2.0.0 · fluxcd/flux2](https://programming.dev/pictrs/image/85147059-4e00-4f4f-aba2-1b00e48eadad.png?format=webp&thumbnail=256)
Highlights This is the first General Availability (GA) release of Flux v2. Flux v2.0.0 comes with the promotion of the GitOps related APIs to v1 and adds horizontal scaling & sharding capabilities ...
![Release v2.0.0 · fluxcd/flux2](https://lemmy.ml/pictrs/image/c9525930-0f4f-4313-9d50-c362c5866d49.png?format=webp&thumbnail=256)
None of those IPs are public so when someone external comes asking for the public IP 129.159.x.x the server will respond that it doesn't have any service running in that IP. When the service is listening to the tailscale interface and you access it through tailscale, your browser is asking the server for the content on 100.64.x.x, the tailscale IP, and so there is indeed a service on that IP. So if you want to provide a service on both the tailscale network and through the public IP, you have to use the IP 0.0.0.0 which means every interface or you can also tell nginx to listen on both the public ip and the tailscale ip. And as the other comment says, you have to allow the port connection in bot the VPS and the Oracle network, the VCN.