Skip to content

[cloud_infra_center]Support bastion insert and clean .#218

Closed
zhengxiaomei123 wants to merge 1 commit intoIBM:mainfrom
zhengxiaomei123:version
Closed

[cloud_infra_center]Support bastion insert and clean .#218
zhengxiaomei123 wants to merge 1 commit intoIBM:mainfrom
zhengxiaomei123:version

Conversation

@zhengxiaomei123
Copy link
Contributor

No description provided.

@zhengxiaomei123 zhengxiaomei123 changed the title [cloud_infra_center][WIP]Support bastion insert and clean . [cloud_infra_center]Support bastion insert and clean . Jun 9, 2023
@zhengxiaomei123 zhengxiaomei123 force-pushed the version branch 2 times, most recently from 6d1868d to b40573b Compare June 9, 2023 10:23
@zhengxiaomei123 zhengxiaomei123 requested a review from bjhuangr June 9, 2023 10:28
@zhengxiaomei123 zhengxiaomei123 force-pushed the version branch 2 times, most recently from 13b2b03 to ba4f20a Compare June 16, 2023 09:26
@ddimatos
Copy link
Member

FYI, happened to look and noticed the lint error is here
image

Signed-off-by: Zheng Xiao Mei <xmzheng@cn.ibm.com>
Copy link
Contributor

@shhull shhull left a comment

Choose a reason for hiding this comment

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

how about our add-compute-node.yaml -e update_bastion=true? we can remove the update_bastion parameter now.

block: |
zone "{{ bastion_reverse }}.in-addr.arpa" {
type master;
file "{{ bastion_reverse }}.in-addr.arpa.zone";
Copy link
Contributor

Choose a reason for hiding this comment

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

it should be file "{{ bastion_reverse }}.in-addr.arpa.{{ cluster_domain_name }}.zone";, right?

@ddimatos ddimatos added the Type: Question Extra attention is needed, help wanted, unsure if it is a bug label Oct 23, 2025
@ddimatos
Copy link
Member

@dibya2804 , can you help on this old PR, decide if its still is needed or close.

@ddimatos ddimatos added Waiting for Reviewer and removed Type: Question Extra attention is needed, help wanted, unsure if it is a bug labels Oct 23, 2025
@ddimatos
Copy link
Member

After speaking with the OCP team, it was determined this PR does not need to be merged and can be closed.

@ddimatos ddimatos closed this Oct 24, 2025
@ddimatos ddimatos added Branch: Do not Merge When a pull request should not be merged for issue noted reasons and removed Waiting for Reviewer labels Oct 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Branch: Do not Merge When a pull request should not be merged for issue noted reasons

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants