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

Missing validation about the min required private and public #295

Open
g-iannelli opened this issue Feb 22, 2023 · 1 comment
Open

Missing validation about the min required private and public #295

g-iannelli opened this issue Feb 22, 2023 · 1 comment
Labels
bug Something isn't working furyctl-ng schema The configuration file schema needs fixing size/S

Comments

@g-iannelli
Copy link
Contributor

cat barebone.eu-west-1.yml| yq -e .spec.infrastructure.vpc.network.subnetsCidrs && AWS_DEFAULT_REGION=us-east-1 AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY furyctl-ng validate config -c barebone.eu-west-1.yml --distro-location 'git::[email protected]:sighupio/fury-distribution.git?depth=1&ref=feature/furyctl-next'
# These are the CIRDs for the private subnets, where the nodes, the pods, and the private load balancers will be created
private: []
# These are the CIDRs for the public subnets, where the public load balancers and the VPN servers will be created
public: []
INFO Downloading distribution...
INFO configuration file validation succeeded
@g-iannelli g-iannelli added bug Something isn't working furyctl-ng labels Feb 22, 2023
@ralgozino ralgozino added the schema The configuration file schema needs fixing label Feb 22, 2023
@omissis omissis added the size/S label Feb 28, 2023
@omissis
Copy link
Contributor

omissis commented Feb 28, 2023

Take some time to investigate the exact requirements with @g-iannelli

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working furyctl-ng schema The configuration file schema needs fixing size/S
Projects
None yet
Development

No branches or pull requests

3 participants