-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configmap for OBC being placed in kube-system? #82
Comments
Just updating the thread with the actual configmap yaml, as it may help my case...
I have no idea why the release is like that. |
An update... I manually created a config file with the correct release and namespace. After rebuilding the env from helm with this configmap in the templates folder, I was able to get my OB/OBC launched as Custom Resources in the correct namespace. Now, the pod I have instructed to use this claim is now up and green, but I'm having trouble identifying any information in the bucket, or vice-versa, I cannot see the data from the pod in AWS's S3 console for this bucket. Basically, how can I see files from the bucket on my pod now that it's using it as a PV? |
I am building a helmchart using this operator. According to the documentation, the configmap referenced by my pod(s) should be available in the same namespace as the OBC, but when I look, it's actually created in kube-system and giving itself the namespace's name and versioning it.
Example:
Any ideas what I might be doing wrong?
The text was updated successfully, but these errors were encountered: