spinnaker
Spinnaker issue
Issue Summary:
Cloud Provider(s):
AWS
Environment:
Feature Area:
Description:
when I add new kubernetes account "hal config provider kubernetes account add k8s-dev --context $CONTEXT" spin-clouddriver-c78bc4db4-6cznw get following error "Could not list namespaces for account k8s-dev: Failed to read [namespace] from : Error in configuration: context was not found for specified context:..."
Steps to Reproduce:
Additional Details:
Please delete the instructions below this line prior to submitting
Instructions:
- An issue is not a place to ask questions. Please use Slack or Stack Overflow.
- Before you open an issue, please check if a similar issue already exists or has been closed before.
- Make sure you have read through the Spinnaker FAQ and Halyard FAQ to provide as much information as possible.
Descriptions:
- Issue Summary: A brief description of what you're seeing.
- Cloud Provider: AWS, GCP, Kubernetes, Azure, Cloud Foundry, etc.
- Environment: As much information about your Spinnaker environment and configuration that might be relevant to the issue. For example: "I am running Spinnaker using the Amazon images to deploy into AWS and GCP."
- Feature Area: Notifications, Pipelines, UI, Jenkins, etc.
- Description: The behavior you expect to see, and the actual behavior.
- Steps to reproduce: Ideally, an isolated way to reproduce the behavior (example: GitHub repository with code isolated to the issue that anyone can clone to observe the problem). If not possible, as much information as possible to see this behavior.
- Additional Details: Additional information such as screenshots and exception logs.
This issue hasn't been updated in 45 days, so we are tagging it as 'stale'. If you want to remove this label, comment:
@spinnakerbot remove-label stale
This issue is tagged as 'stale' and hasn't been updated in 45 days, so we are tagging it as 'to-be-closed'. It will be closed in 45 days unless updates are made. If you want to remove this label, comment:
@spinnakerbot remove-label to-be-closed
This issue is tagged as 'to-be-closed' and hasn't been updated in 45 days, so we are closing it. You can always reopen this issue if needed.