-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Adding ansible operator workflow to the README #667
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
Adding ansible operator workflow to the README #667
Conversation
README.md
Outdated
2. Define new resource APIs by adding Custom Resource Definitions(CRD) (This can be done in the new command) | ||
3. Write the reconciling logic for your object using ansible playbooks and roles. | ||
4. Define the mapping between the CRD definition in the `watches.yaml` file. | ||
5. Use the SDK CLI to build and generate the operator deployment manifests |
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.
Nit: Either keep or remove the period(full stop) at the end of the sentence for all bullet points.
4 has it. 5 doesn't.
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.
LGTM after nit
b8eff6d
to
021106a
Compare
1. Create a new operator project using the SDK Command Line Interface(CLI) | ||
2. Define new resource APIs by adding Custom Resource Definitions(CRD) | ||
3. Define Controllers to watch and reconcile resources | ||
4. Write the reconciling logic for your Controller using the SDK and controller-runtime APIs | ||
5. Use the SDK CLI to build and generate the operator deployment manifests | ||
|
||
The following workflow is for a new **Ansible** operator: |
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.
Don't steps 1, 2, 4 and 5 all largely happen as the result of the operator-sdk
new command? I know it only gives you a single CRD to work with, but that will get most people a long way when they start. I'd describe the workflow more as:
- create new operator with the sdk
- write ansible to do stuff
- use sdk to build and run the operator
- optionally add additional CRDs for specific purposes
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 agree I am going to change better align with @mhrivnak's feedback
021106a
to
c62729a
Compare
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.
LGTM
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.
👍 lgtm
Description of the change:
Adding workflow for the ansible operator in the README.
Motivation for the change:
Making the workflow just as obvious as golang
/cc @hasbro17