Documentation pod status reporting #636
Conversation
jpodivin
force-pushed
the
pod-issues-docs
branch
2 times, most recently
from
b81295a to
cfaec74
Compare
jpodivin
force-pushed
the
pod-issues-docs
branch
from
cfaec74 to
9a5da00
Compare
docs/assemblies/deploying.adoc
Outdated
|
|
||
| Pods launched during deployement throught OpenStackAnsiblEEE managed jobs, | ||
| further referred to as pods, are are marked with label `osdpd=<OpenStackDataPlaneDeployment.Name>` | ||
| and checked for failures. |
There was a problem hiding this comment.
A few typos here, and I don't think it really explains which resources owns the pods. I'd reword it to something like:
During reconciliation of OpenStackDataPlaneDeployment resources, OpenStackAnsibleEE resources are created to manage the ansible executions that configure the EDPM nodes. The OpenStackAnsibleEE resources create Kubernetes Jobs resources, which in turn create Kubernetes Pods that are executing ansible.
Checking the logs of these Jobs and Pods can show ansible failures and help diagnose issues.
There was a problem hiding this comment.
We really ought to mention the ospd= label though.
jpodivin
force-pushed
the
pod-issues-docs
branch
from
9a5da00 to
aa19008
Compare
|
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/af11da4b75494da99338a59f4ce49c57 ✔️ openstack-k8s-operators-content-provider SUCCESS in 45m 34s |
|
recheck |
|
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/44e852bd071a491fa4daeca794f61cb3 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 25m 28s |
|
recheck |
|
/retest |
docs/assemblies/deploying.adoc
Outdated
|
|
||
| Checking the logs of these Jobs and Pods can show ansible failures and help diagnose issues. | ||
|
|
||
| Pods launched during deployement throught OpenStackAnsiblEEE managed jobs, |
There was a problem hiding this comment.
"The pods launched..."
*through
There was a problem hiding this comment.
Document doesn't exist anymore.
docs/assemblies/deploying.adoc
Outdated
| Checking the logs of these Jobs and Pods can show ansible failures and help diagnose issues. | ||
|
|
||
| Pods launched during deployement throught OpenStackAnsiblEEE managed jobs, | ||
| further referred to as pods, are are marked with label `osdpd=<OpenStackDataPlaneDeployment.Name>` |
There was a problem hiding this comment.
drop "further referrred to as pods" clause
docs/assemblies/deploying.adoc
Outdated
|
|
||
| Pods launched during deployement throught OpenStackAnsiblEEE managed jobs, | ||
| further referred to as pods, are are marked with label `osdpd=<OpenStackDataPlaneDeployment.Name>` | ||
| and checked for failures. |
jpodivin
force-pushed
the
pod-issues-docs
branch
from
aa19008 to
5902226
Compare
|
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/20011edcf48b4edc9a04f0c0d316b08c ❌ openstack-k8s-operators-content-provider FAILURE in 7m 31s |
jpodivin
force-pushed
the
pod-issues-docs
branch
from
5902226 to
cc2c306
Compare
|
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/578c237943c34c9db85be5080633db04 ❌ openstack-k8s-operators-content-provider FAILURE in 11m 51s |
jpodivin
force-pushed
the
pod-issues-docs
branch
2 times, most recently
from
decdb45 to
82d65bf
Compare
|
Build failed (check pipeline). Post https://review.rdoproject.org/zuul/buildset/84586c7304ae42118a2a59055191f066 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 31m 06s |
Signed-off-by: Jiri Podivin <[email protected]>
slagle
force-pushed
the
pod-issues-docs
branch
from
82d65bf to
e8650d4
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jpodivin, slagle The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-merge-bot
bot
merged commit 7d61cae
into
openstack-k8s-operators:main
No description provided.