-
Notifications
You must be signed in to change notification settings - Fork 126
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.
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
docs: add KeptnTask ref page; enhance guide chapter for keptn-no-k8s #2103
Conversation
Signed-off-by: Meg McRoberts <[email protected]>
✅ Deploy Preview for keptn-lifecycle-toolkit ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts [email protected] Co-authored-by: RealAnna <[email protected]> Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts [email protected] Co-authored-by: RealAnna <[email protected]> Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts [email protected] Co-authored-by: odubajDT <[email protected]> Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts [email protected] Co-authored-by: odubajDT <[email protected]> Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts [email protected] Co-authored-by: odubajDT <[email protected]> Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts [email protected] Co-authored-by: odubajDT <[email protected]> Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts [email protected] Co-authored-by: odubajDT <[email protected]> Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts [email protected] Co-authored-by: odubajDT <[email protected]> Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts [email protected] Co-authored-by: odubajDT <[email protected]> Signed-off-by: Meg McRoberts <[email protected]>
Signed-off-by: Meg McRoberts [email protected] Co-authored-by: odubajDT <[email protected]> Signed-off-by: Meg McRoberts <[email protected]>
Kudos, SonarCloud Quality Gate passed! |
Keptn Tasks can be triggered for workloads and applications | ||
that are deployed outside of Kubernetes. | ||
For example, Keptn could trigger load and performance tests | ||
for an application that is deployed on a virtual machine. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would add a sentence here to underline the fact that keptn still needs to be installed on a k8s cluster. I think that would make the general scenario a little easier to understand.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I made it "Keptn Tasks running on a Kubernetes cluster..." and some other adjustments to make this more explicit.
For example: | ||
When you have Keptn installed, create a | ||
YAML file that defines what you want to execute | ||
as a `KeptnTaskDefinition` resource.. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as a `KeptnTaskDefinition` resource.. | |
as a `KeptnTaskDefinition` resource. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
|
||
Here though, we must create it ourselves. | ||
Moreover, each time you want to execute a `KeptnTask`, | ||
you must manually create a a new (and uniquely named) `KeptnTask` resource. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you must manually create a a new (and uniquely named) `KeptnTask` resource. | |
you must manually create a new (and uniquely named) `KeptnTask` resource. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
When using Keptn to run tasks for software | ||
that is deployed outside of Kubernetes, | ||
you must create the `KeptnTask` resource manually | ||
and modify it manually for each new run. | ||
Keptn automatically populates the `KeptnTask` resource | ||
for tasks that deploy software on Kubernetes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would switch this paragraph around so that it first tells users the "happy path" which is that they don't need to anything manually with KeptnTasks. And then afterwards, I would add the info about handling apps outside of k8s.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
* **apiVersion** -- API version being used. | ||
` | ||
* **kind** -- Resource type. | ||
Must be set to `KeptnTask` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Must be set to `KeptnTask` | |
Must be set to `KeptnTask` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
## Fields | ||
|
||
* **apiVersion** -- API version being used. | ||
` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
Some comments came in after this PR was merged. These are applied in #2293 . |
This PR and #2089 replace #2086 .
This PR:
KeptnTask
in the yaml-crd-ref section. Normally,KeptnTask
is generated automatically but, in this case, the user must populate and maintain it manually so we need to document the YAML syntax.KeptnTask
example presented in the context of running aKeptnTask
for a non-k8s deployment.28 September review notes:
KeptnTask
resource from my KinD cluster, how does it know which VM/whatever to target?KeptnApp
or workload resources yet theKeptnTask
yaml file does have fields for these. How does the user know what value to use for those fields? Or maybe some of these fields are ignored in this case? We need to clarify this.KeptnTask
fields (such astimeout
) that are also inKeptnTaskDefintion
? If the user uses these, do they need to be sure thatKeptnTask
and the correspondingKeptnTaskDefinition
assign the same value to that field or does Keptn reconcile them or does one of them take precedence over the other?