Removing Snapshot tester #231
Conversation
There was a problem hiding this comment.
@mikemcd3912 test-app can still remain, we want to see if the CSI driver is creating a PVC. You can remove snapshot, snapshot-restore which is not supported in the CSI driver
| @@ -1,4 +0,0 @@ | |||
| apiVersion: kustomize.config.k8s.io/v1beta1 | |||
There was a problem hiding this comment.
This file can be removed. You still need ./eks-anywhere-baremetal/Testers/Core/snapshot-tester/test-app in the snapshot-tester.yaml inorder to test the test-app. I would rather renname snapshot-tester.yaml to meaningful name and update this Kustomization file.
|
GH action failed because we're adding/editing a file to a directory w/o a namespace associated with it, which is expected behavior |
…dating snapshot-tester.yaml to rename and remove snapshot kustomizations
| apiVersion: kustomize.config.k8s.io/v1beta1 | ||
| kind: Kustomization | ||
| resources: | ||
| - claim.yaml |
There was a problem hiding this comment.
Why is this file removed.
There was a problem hiding this comment.
Per our discussion these resource pointer files are unnecessary
Issue #, if available:
N/A
Description of changes:
Removing the snapshot tester from Baremetal to remedy hardcoded storage class issue
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.