OSDOCS#10176: Updates to Terraform files#77311
Conversation
7187fce to
60f8467
Compare
ee27d9e to
ef14f03
Compare
cb239a2 to
f8c1a35
Compare
rosa_hcp/terraform/rosa-hcp-creating-a-cluster-with-customizations-terraform.adoc
Outdated
Show resolved
Hide resolved
rosa_hcp/terraform/rosa-hcp-creating-a-cluster-with-customizations-terraform.adoc
Outdated
Show resolved
Hide resolved
rosa_hcp/terraform/rosa-hcp-creating-a-cluster-with-customizations-terraform.adoc
Show resolved
Hide resolved
...tall_access_delete_clusters/terraform/rosa-classic-creating-a-cluster-quickly-terraform.adoc
Outdated
Show resolved
Hide resolved
f8c1a35 to
e3f9c62
Compare
jneczypor
left a comment
There was a problem hiding this comment.
This is really good for such a large PR! Just a few tiny fixes. Most of my comments and questions revolve around the new naming system for ROSA (classic architecture) and ROSA. You may want to find out how often we are supposed to use parenthetical clarification of (classic architecture). Is it at every mention of ROSA? Just first mention? Will this change when our docs are separate? Now, Classic and HCP is mixed together so we may want to over-clarify a bit to ensure our users know they are on the correct product page. That will involve a lot of conditionalizing, especially in the modules where there is the most re-use. When we have separate docs, it may be less of an issue. Additionally, we will need to inform all our stakeholders and OCP review teams of this change and our guidelines for the name so that they can help us catch the ones we miss.
rosa_hcp/terraform/rosa-hcp-creating-a-cluster-quickly-terraform.adoc
Outdated
Show resolved
Hide resolved
rosa_hcp/terraform/rosa-hcp-creating-a-cluster-quickly-terraform.adoc
Outdated
Show resolved
Hide resolved
...tall_access_delete_clusters/terraform/rosa-classic-creating-a-cluster-quickly-terraform.adoc
Outdated
Show resolved
Hide resolved
...tall_access_delete_clusters/terraform/rosa-classic-creating-a-cluster-quickly-terraform.adoc
Outdated
Show resolved
Hide resolved
...tall_access_delete_clusters/terraform/rosa-classic-creating-a-cluster-quickly-terraform.adoc
Outdated
Show resolved
Hide resolved
...tall_access_delete_clusters/terraform/rosa-classic-creating-a-cluster-quickly-terraform.adoc
Outdated
Show resolved
Hide resolved
114ecf4 to
35aefda
Compare
...delete_clusters/terraform/rosa-classic-creating-a-cluster-with-customizations-terraform.adoc
Show resolved
Hide resolved
...delete_clusters/terraform/rosa-classic-creating-a-cluster-with-customizations-terraform.adoc
Show resolved
Hide resolved
84addea to
c9a10a6
Compare
f3c5d25 to
199ad4a
Compare
JoeAldinger
left a comment
There was a problem hiding this comment.
Some questions and a few suggestions.
| - Name: Creating a ROSA cluster with STS using customizations | ||
| File: rosa-sts-creating-a-cluster-with-customizations | ||
| - Name: Creating a ROSA cluster with STS using Terraform | ||
| - Name: Creating a ROSA (classic architecture) cluster using Terraform |
There was a problem hiding this comment.
I'm not sure how the rule about parenthetical expressions applies to naming here, but I wanted to point it out.
There was a problem hiding this comment.
There are examples in our docs of parentheticals being used in the topic map, usually smaller stuff like (STS) though. This is probably fine
| # | ||
| # Copyright (c) 2023 Red Hat, Inc. | ||
| # | ||
| # Licensed under the Apache License, Version 2.0 (the "License"); |
There was a problem hiding this comment.
I don't think I've ever seen this in the repo where the apache license information is given as part of a code sample. I doubled checked and couldn't find it like this anywhere else. Again, not saying this is wrong just pointing it out.
rosa_hcp/terraform/rosa-hcp-creating-a-cluster-quickly-terraform.adoc
Outdated
Show resolved
Hide resolved
...delete_clusters/terraform/rosa-classic-creating-a-cluster-with-customizations-terraform.adoc
Outdated
Show resolved
Hide resolved
...tall_access_delete_clusters/terraform/rosa-classic-creating-a-cluster-quickly-terraform.adoc
Outdated
Show resolved
Hide resolved
...delete_clusters/terraform/rosa-classic-creating-a-cluster-with-customizations-terraform.adoc
Outdated
Show resolved
Hide resolved
...delete_clusters/terraform/rosa-classic-creating-a-cluster-with-customizations-terraform.adoc
Outdated
Show resolved
Hide resolved
199ad4a to
01c73e4
Compare
|
@EricPonvelle: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
@EricPonvelle I don't see QE or SME ack on this PR. Do you those? |
| - Name: Creating a ROSA cluster with STS using customizations | ||
| File: rosa-sts-creating-a-cluster-with-customizations | ||
| - Name: Creating a ROSA cluster with STS using Terraform | ||
| - Name: Creating a ROSA (classic architecture) cluster using Terraform |
There was a problem hiding this comment.
There are examples in our docs of parentheticals being used in the topic map, usually smaller stuff like (STS) though. This is probably fine
| [id="rosa-classic-cluster-terraform-file-creation_{context}"] | ||
| = Creating your Terraform files locally | ||
|
|
||
| After you set up your link:https://console.redhat.com/openshift/token/rosa[offline {cluster-manager-first} token], you need to create the Terraform files locally to build your cluster. You can create these files by using the following code templates. |
There was a problem hiding this comment.
Is "must" too restrictive here?
https://www.ibm.com/docs/en/ibm-style?topic=word-usage#need-to
|
@EricPonvelle Good work! Merging now. No glaring issues or anything like that. |
|
/cherry-pick enterprise-4.15 |
|
/cherry-pick enterprise-4.16 |
|
@stevsmit: #77311 failed to apply on top of branch "enterprise-4.15": DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@stevsmit: new pull request created: #78104 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
radtriste
left a comment
There was a problem hiding this comment.
@EricPonvelle See my post merge review (sorry for the delay ...)
| [discrete] | ||
| include::modules/rosa-sts-terraform-considerations.adoc[leveloffset=+1] | ||
|
|
||
| include::modules/rosa-sts-overview-of-the-default-cluster-specifications.adoc[leveloffset=+1] |
There was a problem hiding this comment.
Some cluster specifications has no sense in HCP, like:
Control plane node configurationcomponentInfrastructure plane node configurationcomponent- Cluster settings ->
Default EC2 IMDS endpoints Encryption-> No KMS key encryption by default
There was a problem hiding this comment.
@radtriste Do I need to remove the first two items from the HCP flavors of the table? I created this PR that covers the items that I missed with your review: #78211
| # limitations under the License. | ||
| # | ||
| module "vpc" { | ||
| source = "terraform-aws-modules/vpc/aws" |
There was a problem hiding this comment.
Do we want the customer to use the classic modules with BYOVPC as example ?
Because I would rather use rosa-classic vpc submodule to create the VPC
There was a problem hiding this comment.
@andyrepton should I update the VPC modules?
| # limitations under the License. | ||
| # | ||
| module "vpc" { | ||
| source = "terraform-aws-modules/vpc/aws" |
There was a problem hiding this comment.
ROSA HCP should use the rosa-hcp VPC submodule
One example can be found on the repository: https://github.com/terraform-redhat/terraform-rhcs-rosa-hcp/blob/v1.6.2/examples/rosa-hcp-public/main.tf#L51
There was a problem hiding this comment.
@andyrepton should I update the VPC modules?
| * All other AWS resources required to create a ROSA with STS cluster | ||
|
|
||
| include::modules/rosa-terraform-overview.adoc[leveloffset=+1] | ||
| include::modules/rosa-sts-terraform-prerequisites.adoc[leveloffset=+1] |
There was a problem hiding this comment.
This file contains See the Additional resources for more information on the AWS account roles. but I cannot find those additional resources
There was a problem hiding this comment.
@radtriste updated that mistake in this PR as well: #78211
Version(s):
enterprise-4.15+Issue:
OSDOCS-10176
Link to docs preview:
Preparing Terraform to install ROSA clustersThis preparing topic has been hidden. The content was added to each installation guide. We can use this idea to structure a Installation Tools topic.rosa-sts-creating-a-cluster-quickly-terraformtorosa-classic-creating-a-cluster-quickly-terraformQE review:
Additional information:
This PR updates the Terraform files for ROSA (classic architecture) and introduces Terraform for ROSA that uses HCP.