Skip to content
This repository has been archived by the owner on Apr 19, 2023. It is now read-only.

create aws resources as part of installer #550

Open
yithian opened this issue Apr 15, 2019 · 0 comments
Open

create aws resources as part of installer #550

yithian opened this issue Apr 15, 2019 · 0 comments

Comments

@yithian
Copy link

yithian commented Apr 15, 2019

Description

The required AWS resources should be created by the integr8ly installer

Expected Behavior

The installer creates the required AWS resources:

  • An S3 bucket named ${CLUSTER_NAME}-integreatly-s3
  • An IAM group named ${CLUSTER_NAME}-integreatly-s3 (for ease of identification with the bucket, user and policy)
  • An IAM user named ${CLUSTER_NAME}-integreatly-s3 (for ease of identification with the bucket, group and policy)
  • An IAM policy named ${CLUSTER_NAME}-integreatly-s3-policy (for ease of identification with the bucket, group and user) that:
    • is assigned to the group
    • allows users in the group full read/write access to all objects in the s3 bucket
  • An IAM access key and secret for the user, which the rest of the installer will use

A reference can be found in the openshift-ansible-ops repo (if you have access to it).

Actual Behavior

No AWS resources are created, forcing the administrator to create them themselves.

Environment

  • Operating system: (E.g RHEL 7.6 )
    Red Hat Enterprise Linux Server release 7.5 (Maipo)
  • OpenShift version:
    oc v3.11.43
    kubernetes v1.11.0+d4cacc0
    features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://internal.api.achvatal-test.openshift.com:443
openshift v3.11.43
kubernetes v1.11.0+d4cacc0

  • Ansible version:
    ansible 2.7.1

  • Project Version/Tag: (E.g release-1.0.1)
    release-1.3.0

Steps to reproduce

  • run the integr8tly installer
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant