Rework GCP playbooks to use bootkube #10587
Conversation
openshift-ci-robot
added
size/XXL
vrutkovs
force-pushed
the
bootkube-gcp
branch
6 times, most recently
from
c6ca3bc to
7b10d4e
Compare
|
@eparis had mentioned not including the GCP infrastructure playbooks in openshift-ansible as they're not supported for customer use. If we move them elsewhere what's the best place to put them? release repo? origin-ci-tool repo? |
|
@sdodson I think we should stick them in test/ and be explicit about for 'test use only' |
vrutkovs
force-pushed
the
bootkube-gcp
branch
2 times, most recently
from
2e6a7e3 to
a25967c
Compare
|
Decision from this morning's standup is that they'll live in openshift-ansible/test |
vrutkovs
force-pushed
the
bootkube-gcp
branch
4 times, most recently
from
0a256b4 to
b6b3438
Compare
This commit adds code to add hosts to new installer cluster.
vrutkovs
force-pushed
the
bootkube-gcp
branch
from
b6b3438 to
651d26c
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: michaelgugino, vrutkovs The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
| copy: | ||
| content: "{{ (lookup('file', openshift_gcp_iam_service_account_keyfile ) | from_json ).private_key }}" | ||
| dest: /tmp/gce.pem | ||
| mode: 0600 |
There was a problem hiding this comment.
mode: 0600 was overly strict when I ran this locally (uncontainerized). Modules trying to open the file would have permission denied.
There was a problem hiding this comment.
@patrickdillon This is possibly due to incorrect use of 'become'.
6 participants
Requires
openshift_gcp_bootstrap_ignition_file- a location of bootstrap ignition file.TODO:
Port the rest of the scripted gcloud commands to ansibleThese modules are community-supported and should not be actively used
test/gcp