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

Add bastion #198

Merged
3 commits merged into from Jan 25, 2023
Merged

Add bastion #198

3 commits merged into from Jan 25, 2023

Conversation

ghost
Copy link

@ghost ghost commented Nov 30, 2022

What type of PR is this?
/kind feature

What this PR does / why we need it:
Add optional bastion
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #35

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

TODOs:

  • squashed commits
  • includes documentation
  • adds unit tests

@ghost ghost marked this pull request as draft December 2, 2022 10:05
@ghost ghost marked this pull request as ready for review January 17, 2023 17:04
@ghost ghost requested review from outscale-mdr and outscale-hmi January 17, 2023 17:09
@ghost ghost changed the title DRAFT: Add bastion Add bastion Jan 17, 2023
Comment on lines 167 to 172
for _, subnetSpec := range subnetsSpec {
subnetName := subnetSpec.Name
ipSubnetRange := subnetSpec.IpSubnetRange
clusterScope.Info("Get IpSubnetRange", "ipSubnetRange", ipSubnetRange)
clusterScope.Info("Get subnetName", "subnetName", subnetName)
}
Copy link
Contributor

Choose a reason for hiding this comment

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

What is the use of this for loop ?
Does it matter if ipSubnetRange is overrided if there are multiple subnets ?

Copy link
Author

Choose a reason for hiding this comment

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

No.

Copy link
Author

Choose a reason for hiding this comment

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

No it is now remove

Comment on lines +186 to +181
_, err := infrastructurev1beta1.ValidateIops(rootDiskIops)
if err != nil {
return bastionTagName, err
}
Copy link
Contributor

Choose a reason for hiding this comment

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

I recently discovered that the ratio iops/size should not execeed 300, mayeb check that in the future

Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Author

Choose a reason for hiding this comment

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

Ok good idea:
#216

@ghost ghost merged commit 6eaf68e into outscale:main Jan 25, 2023
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Have a bastion to connect to control plane or worker node
2 participants