mirrors/kube-prometheus
1
0
Fork 0
mirror of https://github.com/prometheus-operator/kube-prometheus.git synced 2025-10-24 21:51:18 +02:00
Code Issues Projects Releases Wiki Activity

Merge pull request #1521 from paulfantom/recommend-server-side-apply

Browse Source 
*: point to using server-side apply with kubectl as a solution to large CRDs
This commit is contained in:
Arthur Silva Sens 2021-11-29 10:05:39 -03:00 committed by GitHub
commit 8ed8f70148
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 11 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@ -110,14 +110,14 @@ Though for a quickstart a compiled version of the Kubernetes [manifests](manifes
```shell ```shell
# Create the namespace and CRDs, and then wait for them to be available before creating the remaining resources # Create the namespace and CRDs, and then wait for them to be available before creating the remaining resources
kubectl create -f manifests/setup kubectl apply --server-side -f manifests/setup
until kubectl get servicemonitors --all-namespaces ; do date; sleep 1; echo ""; done until kubectl get servicemonitors --all-namespaces ; do date; sleep 1; echo ""; done
kubectl create -f manifests/ kubectl apply -f manifests/
``` ```
We create the namespace and CustomResourceDefinitions first to avoid race conditions when deploying the monitoring components. We create the namespace and CustomResourceDefinitions first to avoid race conditions when deploying the monitoring components.
Alternatively, the resources in both folders can be applied with a single command Alternatively, the resources in both folders can be applied with a single command
`kubectl create -f manifests/setup -f manifests`, but it may be necessary to run the command multiple times for all components to `kubectl apply --server-side -f manifests/setup -f manifests`, but it may be necessary to run the command multiple times for all components to
be created successfullly. be created successfullly.
* And to teardown the stack: * And to teardown the stack:
@ -274,12 +274,16 @@ Now simply use `kubectl` to install Prometheus and Grafana as per your configura
```shell ```shell
# Update the namespace and CRDs, and then wait for them to be available before creating the remaining resources # Update the namespace and CRDs, and then wait for them to be available before creating the remaining resources
$ kubectl apply -f manifests/setup $ kubectl apply --server-side -f manifests/setup
$ kubectl apply -f manifests/ $ kubectl apply -f manifests/
``` ```
> Note that due to some CRD size we are using kubeclt server-side apply feature which is generally available since
> kubernetes 1.22. If you are using previous kubernetes versions this feature may not be available and you would need to
> use `kubectl create` instead.
Alternatively, the resources in both folders can be applied with a single command Alternatively, the resources in both folders can be applied with a single command
`kubectl apply -Rf manifests`, but it may be necessary to run the command multiple times for all components to `kubectl apply --server-side -Rf manifests`, but it may be necessary to run the command multiple times for all components to
be created successfullly. be created successfullly.
Check the monitoring namespace (or the namespace you have specific in `namespace: `) and make sure the pods are running. Prometheus and Grafana should be up and running soon. Check the monitoring namespace (or the namespace you have specific in `namespace: `) and make sure the pods are running. Prometheus and Grafana should be up and running soon.

2
developer-workspace/common/deploy-kube-prometheus.sh
View File

@ -1,6 +1,6 @@
#!/bin/bash #!/bin/bash
kubectl apply -f manifests/setup kubectl apply --server-side -f manifests/setup
# Safety wait for CRDs to be working # Safety wait for CRDs to be working
sleep 30 sleep 30