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

Extend workload pools to include ingress firewall and ip allocations #6

Merged
merged 6 commits into from
Oct 22, 2024

Conversation

nsricardor
Copy link
Contributor

This PR extends workload pools to include ingress firewall and IP allocations and add a status so users can discover the hostname and IP addresses of provisioned machines

@nsricardor nsricardor marked this pull request as draft October 18, 2024 08:22
@nsricardor nsricardor marked this pull request as ready for review October 21, 2024 10:59
Copy link
Member

@spjmurray spjmurray left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a couple tweaks that can improve things, but I'm not going to hold you up for now...

@@ -256,6 +424,38 @@ components:
machine:
flavorId: c7568e2d-f9ab-453d-9a3a-51375f78426b
replicas: 3
firewall:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Examples are obviously the best illustration to review 😸

Looks good so far. I'd have a word with Adam, the firewall rules may need a description to make the UI happier.

publicIP:
description: Machine public IP address.
type: string
status:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

port:
$ref: '#/components/schemas/firewallRulePort'
cidr:
description: A list of CIDR blocks to allow, it might be any IPv4 or IPv6 in CIDR notation.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Surprise I've not done this yet, but we should probably have a type definition in core for an IPv4 CIDR with the required regular expression patter matcher too.

@spjmurray spjmurray merged commit b3dc4ad into unikorn-cloud:main Oct 22, 2024
4 checks passed
@nsricardor nsricardor deleted the ingressfw_ipallocation branch October 23, 2024 07:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants