Skip to content
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

Feat(clouddriver/halyard): Support larger number of accounts for Kubernetes Clouddriver #3959

Open
rebalag opened this issue Feb 11, 2019 · 4 comments

Comments

Projects
None yet
4 participants
@rebalag
Copy link

commented Feb 11, 2019

Issue Summary:

Deploying HA mode for Clouddriver reaches secret size limit with small number of account when the accounts are configured with namespace list and omitkinds list. Need to have the ability to configure 100s of accounts without hitting this limit from kubernetes secrets (1MB max)

Cloud Provider(s):

Kubernetes

Environment:

Clouddriver configured in HA environment deployed using Halyard

Feature Area:

Halyard configuration and deploy of Kubernetes accounts

Description:

hal deploy generates clouddriver.yml, clouddriver-rw.yml (-ro.yml, -caching.yml) with accounts configured. With each account configuration ~1kB, and local Kubernetes deployment restricting secret to 250kB limits the number of accounts to less than 100 that can be configured and deployed using Halyard.

Additional Details:

ConfigMaps have higher limits for sizes and can be used for account configurations for higher limit than the secrets. Each account can be tagged as insecure that can then be allocated to configmap with clouddriver-insecure.yml

Currently, Halyard creates a secret with clouddriver.yml, clouddriver-rw.yml with same information doubling the size of the secret which can be removed and apply the accounts to only one of the configuration files.

If it is possible to zip the secret then it will allow for much larger hal config file than it is supported now.

@ajordens

This comment has been minimized.

Copy link
Contributor

commented Feb 12, 2019

Over to @spinnaker/google for feedback.

@ttomsu

This comment has been minimized.

Copy link
Contributor

commented Feb 13, 2019

Filed #3968 for the broader FR to allow Halyard to deploy using Configmaps

@spinnakerbot

This comment has been minimized.

Copy link

commented Mar 30, 2019

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

@spinnakerbot spinnakerbot added the stale label Mar 30, 2019

@spinnakerbot

This comment has been minimized.

Copy link

commented May 14, 2019

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.