Skip to content

Commit bf5a367

Browse files
authored
Merge branch 'main' into add_fallback_strategy_for_per_node_strategy
2 parents 0f878f0 + d276245 commit bf5a367

File tree

2 files changed

+52
-0
lines changed

2 files changed

+52
-0
lines changed
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
apiVersion: v1
2+
kind: Pod
3+
metadata:
4+
labels:
5+
app.kubernetes.io/name: opentelemetry-operator
6+
control-plane: controller-manager
7+
namespace: ($OTEL_NAMESPACE)
8+
status:
9+
containerStatuses:
10+
- name: kube-rbac-proxy
11+
ready: true
12+
started: true
13+
- name: manager
14+
ready: true
15+
started: true
16+
phase: Running
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
apiVersion: chainsaw.kyverno.io/v1alpha1
2+
kind: Test
3+
metadata:
4+
name: operator-restart
5+
spec:
6+
# Running the test serially as its disruptive causing operator pod restart
7+
concurrent: false
8+
steps:
9+
- name: Delete operator pod
10+
try:
11+
- command:
12+
entrypoint: kubectl
13+
args:
14+
- get
15+
- pods
16+
- -A
17+
- -l control-plane=controller-manager
18+
- -l app.kubernetes.io/name=opentelemetry-operator
19+
- -o
20+
- jsonpath={.items[0].metadata.namespace}
21+
outputs:
22+
- name: OTEL_NAMESPACE
23+
value: ($stdout)
24+
- delete:
25+
ref:
26+
apiVersion: v1
27+
kind: Pod
28+
namespace: ($OTEL_NAMESPACE)
29+
labels:
30+
control-plane: controller-manager
31+
app.kubernetes.io/name: opentelemetry-operator
32+
# Adding 10s sleep here cause sometimes the pod will be in running state for a while but can fail later if there is any issue with the component startup.
33+
- sleep:
34+
duration: 10s
35+
- assert:
36+
file: assert-operator-pod.yaml

0 commit comments

Comments
 (0)