Minio Communications Update

Currently Minio is not extremely useful due to a combination of networkPolicies and lack of VirtualService for the non-console service (the S3 compatible endpoint). We will need to add a networkPolicy to allow things in cluster to hit the minio service and add a virtualService that points to this same service for external access. For the VS name... maybe minio-api.bigbang.dev or maybe rename the existing VS to minio-console.bigbang.dev and use minio.bigbang.dev as the default?

AC:

• Networkpolicies enabled in test values
• New virtual service added for the s3 compatible endpoint
• New networkPolicy to allow anything in cluster to hit minio svc

added teamXForce label

changed the description

added kindfeature label

added minio label

NOTE: I believe we will be blocked on enabling Velero tests in BB CI until this is complete. Adding to next milestone.

changed milestone to %1.22.0

changed iteration to Big Bang Iterations Nov 16, 2021 - Nov 29, 2021

This is a requirement to get Velero tests working in BB CI, which is why it was added to the next sprint.

added priority6 label

set weight to 2

assigned to @mark.sanchez

created merge request !51 (merged) to address this issue

mentioned in merge request !51 (merged)

added statusdoing label

Successfully tested communications between Velero and Minio. Velero test values need to be changed and minio bucket needs to be created for communication. This worked with current network policies.

Velero values used:

    values:
      # Set provider name and backup storage location bucket name
      configuration:
        provider: aws
        # TODO: Bucket for this
        backupStorageLocation:
          bucket: velero-test
          # prefix: ci
          default: true
          config: &minio-config
            region: velero
            # profile: test
            insecureSkipTLSVerify: "true"
            s3ForcePathStyle: "true"
            s3Url: &minio-address http://minio.minio.svc

Created and Tested VS without network policies and was able to connect to minio api. Added allow-to-istio-ingressgateway Network policy and can access minio api with NPs enabled

Next steps is template VS for minio api and create additional network policies so for access internal to cluster.

marked the checklist item Networkpolicies enabled in test values as completed

marked the checklist item New virtual service added for the s3 compatible endpoint as completed

marked the checklist item New networkPolicy to allow anything in cluster to hit minio svc as completed

added statusreview label and removed statusdoing label

Package changes merged.

Bigbang MR is showing errors on the cypress test. Need to look into the issue.

https://repo1.dso.mil/platform-one/big-bang/bigbang/-/jobs/8172252#L2212

removed statusreview label

unassigned @mark.sanchez

assigned to @jtabalon

added statusdoing label

mentioned in merge request !52 (merged)

assigned to @mark.sanchez

added statusreview label and removed statusdoing label

closed

removed statusreview label