-
Notifications
You must be signed in to change notification settings - Fork 84
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
Update intro #320
Update intro #320
Conversation
26b91c0
to
f2e585b
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.
How about this.
docs/introduction.md
Outdated
@@ -29,8 +29,7 @@ Importantly, RKE2 does not rely on Docker as RKE1 does. RKE1 leveraged Docker fo | |||
## Why two names? | |||
It is known as RKE2 as it is the next iteration of the Rancher Kubernetes Engine for datacenter use cases. The distribution runs standalone or integrated into Rancher. Automated provisioning of new RKE2 clusters is available in Rancher v2.6+. | |||
|
|||
It is also known as RKE Government in order to convey another use case and sector it currently targets. | |||
|
|||
It has also been known as RKE Government in order to convey another use case and sector it currently targets. |
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.
It has also been known as RKE Government in order to convey another use case and sector it currently targets. |
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 modified it slightly
f2e585b
to
312f92c
Compare
Signed-off-by: manuelbuil <[email protected]>
Two changes:
1 - Updates the definition of RKE2 to avoid confusion
2 - Updates the CIS profiles to newer ones