Skip to content

Adds Istio information for sleep mode #1491

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.

Sign up for GitHub

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

Merged
Piotr1215 merged 2 commits into from
Dec 18, 2025
Merged

Adds Istio information for sleep mode #1491

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ca9eef8
Adds Istio information for sleep mode
zerbitx Dec 12, 2025
e905fb4
correct virtual cluster instance references and clear up Ingress and …
zerbitx Dec 17, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 4 additions & 9 deletions platform/_partials/sleep/activity-detection.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,28 +16,23 @@ env:

All virtual cluster Kubernetes API requests that are made through the platform count as activity in the {props.name}.


<!-- vale off -->
```mermaid
flowchart LR;
kubectl("<code>$ kubectl get pod my-pod</code>") --> Platform

Platform("vCluster Platform")

Platform --> Cluster("Connected Cluster <br/> Kubernetes API Server")
Cluster --> Pod("apiVersion: v1<br/>kind: Pod<br/>metadata:<br/> name: my-pod<br/>...")

class kubectl code
class Pod yaml
class Platform platform
Cluster --> Pod("<div style='text-align:left; margin:0px;'>apiVersion:&nbsp;v1<br/>kind: Pod<br/>metadata:<br/>&nbsp;&nbsp;name: my-pod<br/></div>")
```
<!-- vale on -->

If your kube-context points to the platform's API server as a proxy before the actual connected cluster's API server, every `kubectl` request will be an activity and reset the inactivity timeout.

### Ingress Requests

For ingress-nginx based ingresses, activity detection also works automatically. Other ingress controllers are currently not supported. For nginx based ingresses, the platform will add a special annotation to each ingress that will track activity and reset the timer when a request is made to that ingress.
For [ingress-nginx](https://github.com/kubernetes/ingress-nginx/tree/main) based Ingresses and [Istio](https://istio.io/) Gateways, activity detection works automatically.
For nginx based ingresses, the platform adds the [mirror-target](https://github.com/kubernetes/ingress-nginx/blob/main/docs/user-guide/nginx-configuration/annotations.md#mirror) annotation to each ingress that will track activity and reset the timer when a request is made to that ingress.
For Istio, the metrics from the istio-proxy container are used to determine activity.

<br></br>

Expand Down
12 changes: 5 additions & 7 deletions platform_versioned_docs/version-4.3.0/_partials/sleep/activity-detection.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,23 +8,21 @@ flowchart LR;
Platform("vCluster Platform")

Platform --> Cluster("Connected Cluster <br/> Kubernetes API Server")
Cluster --> Pod("apiVersion: v1<br/>kind: Pod<br/>metadata:<br/> name: my-pod<br/>...")

class kubectl code
class Pod yaml
class Platform platform
Cluster --> Pod("<div style='text-align:left; margin:0px;'>apiVersion:&nbsp;v1<br/>kind: Pod<br/>metadata:<br/>&nbsp;&nbsp;name: my-pod<br/></div>")
```

If your kube-context points to the platform's API server as a proxy before the actual connected cluster's API server, every `kubectl` request will be an activity and reset the inactivity timeout.

### Ingress Requests

For ingress-nginx based ingresses, activity detection also works automatically. Other ingress controllers are currently not supported. For nginx based ingresses, the platform will add a special annotation to each ingress that will track activity and reset the timer as soon as a request is made to that ingress.
For [ingress-nginx](https://github.com/kubernetes/ingress-nginx/tree/main) based Ingresses and [Istio](https://istio.io/) Gateways, activity detection works automatically.
For nginx based ingresses, the platform adds the [mirror-target](https://github.com/kubernetes/ingress-nginx/blob/main/docs/user-guide/nginx-configuration/annotations.md#mirror) annotation to each ingress that will track activity and reset the timer when a request is made to that ingress.
For Istio, the metrics from the istio-proxy container are used to determine activity.

<br></br>

:::info Ingress Wakeup

vCluster Platform supports waking up a {props.name} through an ingress independent of the underlying ingress controller. Just navigate to the ingress host and you should see a wakeup page for the {props.name}.

:::
:::
10 changes: 4 additions & 6 deletions platform_versioned_docs/version-4.4.0/_partials/sleep/activity-detection.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,18 +24,16 @@ flowchart LR;
Platform("vCluster Platform")

Platform --> Cluster("Connected Cluster <br/> Kubernetes API Server")
Cluster --> Pod("apiVersion: v1<br/>kind: Pod<br/>metadata:<br/> name: my-pod<br/>...")

class kubectl code
class Pod yaml
class Platform platform
Cluster --> Pod("<div style='text-align:left; margin:0px;'>apiVersion:&nbsp;v1<br/>kind: Pod<br/>metadata:<br/>&nbsp;&nbsp;name: my-pod<br/></div>")
```

If your kube-context points to the platform's API server as a proxy before the actual connected cluster's API server, every `kubectl` request will be an activity and reset the inactivity timeout.

### Ingress Requests

For ingress-nginx based ingresses, activity detection also works automatically. Other ingress controllers are currently not supported. For nginx based ingresses, the platform will add a special annotation to each ingress that will track activity and reset the timer when a request is made to that ingress.
For [ingress-nginx](https://github.com/kubernetes/ingress-nginx/tree/main) based Ingresses and [Istio](https://istio.io/) Gateways, activity detection works automatically.
For nginx based ingresses, the platform adds the [mirror-target](https://github.com/kubernetes/ingress-nginx/blob/main/docs/user-guide/nginx-configuration/annotations.md#mirror) annotation to each ingress that will track activity and reset the timer when a request is made to that ingress.
For Istio, the metrics from the istio-proxy container are used to determine activity.

<br></br>

Expand Down
10 changes: 4 additions & 6 deletions platform_versioned_docs/version-4.5.0/_partials/sleep/activity-detection.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,18 +24,16 @@ flowchart LR;
Platform("vCluster Platform")

Platform --> Cluster("Connected Cluster <br/> Kubernetes API Server")
Cluster --> Pod("apiVersion: v1<br/>kind: Pod<br/>metadata:<br/> name: my-pod<br/>...")

class kubectl code
class Pod yaml
class Platform platform
Cluster --> Pod("<div style='text-align:left; margin:0px;'>apiVersion:&nbsp;v1<br/>kind: Pod<br/>metadata:<br/>&nbsp;&nbsp;name: my-pod<br/></div>")
```

If your kube-context points to the platform's API server as a proxy before the actual connected cluster's API server, every `kubectl` request will be an activity and reset the inactivity timeout.

### Ingress Requests

For ingress-nginx based ingresses, activity detection also works automatically. Other ingress controllers are currently not supported. For nginx based ingresses, the platform will add a special annotation to each ingress that will track activity and reset the timer when a request is made to that ingress.
For [ingress-nginx](https://github.com/kubernetes/ingress-nginx/tree/main) based Ingresses and [Istio](https://istio.io/) Gateways, activity detection works automatically.
For nginx based ingresses, the platform adds the [mirror-target](https://github.com/kubernetes/ingress-nginx/blob/main/docs/user-guide/nginx-configuration/annotations.md#mirror) annotation to each ingress that will track activity and reset the timer when a request is made to that ingress.
For Istio, the metrics from the istio-proxy container are used to determine activity.

<br></br>

Expand Down
Loading