Skip to content

Add record for api-int to baremetal bridge#531

Closed
stbenjam wants to merge 1 commit intoopenshift-metal3:masterfrom
stbenjam:api-int
Closed

Add record for api-int to baremetal bridge#531
stbenjam wants to merge 1 commit intoopenshift-metal3:masterfrom
stbenjam:api-int

Conversation

@stbenjam
Copy link
Copy Markdown
Member

In 4.1, api-int is used by ignition so the record needs to exist in the baremetal network.

@russellb
Copy link
Copy Markdown
Member

In 4.1, api-int is used by ignition so the record needs to exist in the baremetal network.

I understand that this is needed to test the next rebase. That's fine.

I'd like to see a solution for adding api-int that doesn't include adding it as another external DNS requirement. @celebdor @cybertron

@stbenjam
Copy link
Copy Markdown
Member Author

This openshift-metal3/kni-installer#77 will maybe work without the external record, going to test that.

@stbenjam stbenjam closed this May 13, 2019
@stbenjam stbenjam deleted the api-int branch May 13, 2019 14:51
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