Skip to content
This repository was archived by the owner on Jun 12, 2023. It is now read-only.

Commit 06612d6

Browse files
authored
Merge pull request #83 from fromanirh/condition-docs
Condition docs
2 parents 5c6c0d6 + b7a915d commit 06612d6

File tree

2 files changed

+70
-0
lines changed

2 files changed

+70
-0
lines changed
File renamed without changes.

docs/dev/status-conditions.md

+70
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
# Checking SSP Operator Status conditions
2+
3+
1. Deploy ssp-operator
4+
2. Wait few minutes until all components are deployed
5+
3. run `oc describe KubevirtNodeLabellerBundle`
6+
7+
example output:
8+
```
9+
Name: kubevirt-node-labeller-bundle
10+
Namespace: kubevirt
11+
Labels: <none>
12+
Annotations: kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"kubevirt.io/v1","kind":"KubevirtNodeLabellerBundle","metadata":{"annotations":{},"name":"kubevirt-node-labeller-bundle","namespace":"kub...
13+
API Version: kubevirt.io/v1
14+
Kind: KubevirtNodeLabellerBundle
15+
Metadata:
16+
Creation Timestamp: 2019-08-22T12:21:22Z
17+
Generation: 1
18+
Resource Version: 8894
19+
Self Link: /apis/kubevirt.io/v1/namespaces/kubevirt/kubevirtnodelabellerbundles/kubevirt-node-labeller-bundle
20+
UID: 5a320a2d-c4d7-11e9-95d3-5254006f4280
21+
Spec:
22+
Version: v0.0.5
23+
Status:
24+
Conditions:
25+
Last Transition Time: 2019-08-22T12:23:01Z
26+
Message: Node-labeller is progressing.
27+
Reason: progressing
28+
Status: False
29+
Type: Progressing
30+
Last Transition Time: 2019-08-22T12:22:37Z
31+
Message: Node-labeller is available.
32+
Reason: available
33+
Status: True
34+
Type: Available
35+
Last Transition Time: 2019-08-22T12:22:37Z
36+
Message: Node-labeller is degraded.
37+
Reason: degraded
38+
Status: False
39+
Type: Degraded
40+
Ansible Result:
41+
Changed: 0
42+
Completion: 2019-08-22T12:25:33.424451
43+
Failures: 0
44+
Ok: 8
45+
Skipped: 0
46+
Last Transition Time: 2019-08-22T12:21:29Z
47+
Message: Awaiting next reconciliation
48+
Reason: Successful
49+
Status: True
50+
Type: Running
51+
Events: <none>
52+
```
53+
54+
4. check status.conditions - it should contain conditions:
55+
```
56+
Progressing - False
57+
Available - True
58+
Degraded - False
59+
```
60+
61+
5. the same you can do with KubevirtTemplateValidator and KubevirtCommonTemplatesBundle (this CR will NOT contain degraded condition, because it makes no sense to put it there, because in every iteration templates are "reinstalled")
62+
63+
6. you can of course delete pods and test if it changes conditions (but take in account, every iteration is slow, so when you delete e.g. node-labeller, it can be recreated between the iterations and ansible will not notice that it was deleted).
64+
The Easiest way is to create e.g. 2 nodes, let node-labeller to be deployed on both nodes and then disable one (`sudo ifconfig eth0 down && sleep 10 && sudo ifconfig eth0 up`)
65+
and then wait for [300x10 second](https://github.com/MarSik/kubevirt-ssp-operator/pull/76/files#diff-d1fae8c4046ebdb431e9b097881fc1b7R39 I think we should lower this constant) after that it should set conditions:
66+
```
67+
Progressing - True
68+
Available - False
69+
Degraded - True
70+
```

0 commit comments

Comments
 (0)