Skip to content

Fix demo #24

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
merged 1 commit into from
Jul 30, 2024
Merged

Fix demo #24

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
11 changes: 7 additions & 4 deletions managed-services/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,22 +92,25 @@ and then ask Sveltos to:
- deploy it to the production cluster

```
kubectl create configmap production-postgres --from-file=https://raw.githubusercontent.com/projectsveltos/demos/main/managed-services/deploy-job-to-production.yaml
kubectl apply -f https://raw.githubusercontent.com/projectsveltos/demos/main/managed-services/deploy-job-to-production.yaml
```

With kubectl pointing to the production cluster
With kubectl pointing to the production cluster we can verify the Job was created and successfully completed (a table was created in the Postgres on the clusters were services are deployed)

```
KUBECONFIG=<production-kubeconfig> kubectl get jobs -A
todo todo-table 1/1 3s 11s
```

We can deploy same Job to pre-production cluster. This Jop will create a table to the pre-production Postgres running on the managed-services-cluster
We can deploy same Job to pre-production cluster.

```
kubectl create configmap production-postgres --from-file=https://raw.githubusercontent.com/projectsveltos/demos/main/managed-services/deploy-job-to-pre-production.yaml
kubectl apply -f https://raw.githubusercontent.com/projectsveltos/demos/main/managed-services/deploy-job-to-pre-production.yaml

```

With kubectl pointing to the pre-production cluster we can verify the Job was created and successfully completed (a table was created in the Postgres on the clusters were services are deployed)

```
KUBECONFIG=<pre-production-kubeconfig> kubectl get jobs -A
NAMESPACE NAME COMPLETIONS DURATION AGE
Expand Down