fix: updated Kibana app endpoint to private

[Ak-sky]

Description

• Updated Kibana app endpoint to private.
  Git Issue

Release required?

• No release
• Patch release (x.x.X)
• Minor release (x.X.x)
• Major release (X.x.x)

Release notes content

• The Kibana application will be configured to use a private endpoint by default for receiving requests. This behavior can be customized by modifying the kibana_visibility variable.
• Changing the Kibana visibility from private to public using the kibana_visibility variable makes it publicly accessible but disables access via IBM Cloud private network, with immediate effect and potential security implications.

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

• If relevant, a test for the change is included or updated with this PR.
• If relevant, documentation for the change is included or updated with this PR.

For mergers

• Use a conventional commit message to set the release level. Follow the guidelines.
• Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
• Use the Squash and merge option.

[Ak-sky]

/run pipeline

[Ak-sky]

/run pipeline

[ocofaigh]

What impact does this have on upgrade? Is it going to tear down anything? Re-deploy kibana? Lets ensure we are deploying kibana as part of DA upgrade test for a start

[Ak-sky]

What impact does this have on upgrade? Is it going to tear down anything? Re-deploy kibana? Lets ensure we are deploying kibana as part of DA upgrade test for a start

It is only going to update the endpoint for the Kibana app from local_public to local_private. This means any existing users will no longer be able to access the Kibana app from the public internet and is only accessible via the IBM Cloud private network.

[Ak-sky]

Also, due to the schematics limitations, we cannot run the upgrade test.

[Ak-sky]

What impact does this have on upgrade? Is it going to tear down anything? Re-deploy kibana? Lets ensure we are deploying kibana as part of DA upgrade test for a start

It is only going to update the endpoint for the Kibana app from local_public to local_private. This means any existing users will no longer be able to access the Kibana app from the public internet and is only accessible via the IBM Cloud private network.

@ocofaigh , does this come under breaking change?

[ocofaigh]

@Ak-sky It depends on what actions occur. Will the kibana app be redeployed to to the config error (meaning dashbaord will go down). It seems the upgrade test is not deploying kibana. I think you need to change it so it does so we test that use case

[Ak-sky]

@Ak-sky It depends on what actions occur. Will the kibana app be redeployed to to the config error (meaning dashbaord will go down). It seems the upgrade test is not deploying kibana. I think you need to change it so it does so we test that use case

It does not redeploy Kibana, it is just an update of app endpoint.
Also DA runs in schematics so unable to do upgrade test.

[ocofaigh]

@Ak-sky If it was using public before, then how did the dashboard ever work since our DA only deploys private only ES instance?
ah sorry this is the code engine app endpoint

[ocofaigh]

So @Ak-sky how is somebody supposed to hit the kibana url private endpoint in their browser? We will wan't to document that? Is it even possible to set up a VPN that can access it?

[Ak-sky]

So @Ak-sky how is somebody supposed to hit the kibana url private endpoint in their browser? We will wan't to document that? Is it even possible to set up a VPN that can access it?

@ocofaigh, we need to discuss about this, I will add this topic for deep dive.

[Ak-sky]

/run pipeline

[ocofaigh]

Left some comments. Also dont forget to add new vars to ibm_catalog.json. And use custom dropdown for the endpoint one

[ocofaigh]

Wait for #363 to be merged fist

[Ak-sky]

/run pipeline