Resolve "SSO Startup Fails Starting With 1.18.0-bb.3"

General MR

Summary

This MR satisfies the issue presented in #204 (closed) without causing the issue discussed in #213 (closed).

Relevant logs/screenshots

Combining the values from <bigbang-git-root>/docs/assets/configs/example/dev-sso-values.yaml with the following values overlay:

elasticsearchKibana:
  enabled: true
  istio:
    enabled: true
    elasticsearch:
      enabled: true
  git:
    branch: 213-ek-mtls-fix
    tag: null

produces no pod startup errors but assures mTLS connectivity visible within Kiali:

Additionally, the elasticsearch endpoint is reachable via curl:

❯ curl -u elastic:$(kubectl get secrets -n logging logging-ek-es-elastic-user -o go-template='{{.data.elastic | base64decode}}') https://elasticsearch.dev.bigbang.mil/
{
  "name" : "logging-ek-es-data-2",
  "cluster_name" : "logging-ek",
  "cluster_uuid" : "EsvbwhueRB-kW15fEehVYg",
  "version" : {
    "number" : "8.15.1",
    "build_flavor" : "default",
    "build_type" : "docker",
    "build_hash" : "253e8544a65ad44581194068936f2a5d57c2c051",
    "build_date" : "2024-09-02T22:04:47.310170297Z",
    "build_snapshot" : false,
    "lucene_version" : "9.11.1",
    "minimum_wire_compatibility_version" : "7.17.0",
    "minimum_index_compatibility_version" : "7.0.0"
  },
  "tagline" : "You Know, for Search"
}

Linked Issue

Closes #213 (closed)

Upgrade Notices

N/A

changed milestone to %2.37.0

added elasticsearch kindbug statusdoing teamObservability triage-priority labels

assigned to @zcallahan

changed milestone to %2.38.0

marked this merge request as ready

changed the description

added statusreview label and removed statusdoing triage-priority labels

requested review from @kliu, @blairbowden, @peter.sigur, @steven.donald, @kscheunemann, and @piotr.machaj

added 7 commits

• 95c82d08...84f32f7b - 4 commits from branch main
• 85293e86 - fix(istio): skip TLS verification from envoy to workload in ES pod
• 08e08815 - fix(istio): override scheme to http for elastic host in kibana when istio enabled
• 3b98addf - chore(changelog): updated changelog and generated readme

Compare with previous version

update: waiting on a renovate update for EK that's having some issues to be merged in before merging this guy.

added 10 commits

• 3b98addf...e6bcadaf - 6 commits from branch main
• cb0942c2 - fix(istio): skip TLS verification from envoy to workload in ES pod
• 8bf0c5dc - fix(istio): override scheme to http for elastic host in kibana when istio enabled
• ee94a6d1 - chore(changelog): updated changelog and generated readme
• be3d2ca5 - fix(lint): corrected linter errors from upstream README template

Compare with previous version

resolved all threads

requested review from @bjacksonfv

added 5 commits

• be3d2ca5...b9bb6ea4 - 2 commits from branch main
• cdbe221d - fix(istio): skip TLS verification from envoy to workload in ES pod
• 53ecabd0 - fix(istio): override scheme to http for elastic host in kibana when istio enabled
• b6b2f4d9 - chore(changelog): added changelog entry and generated README

Compare with previous version

changed milestone to %2.39.0

validated that the kibana objects has elasticsearch.hosts config. and the insecureSkipVerify is set on the destinationrule

approved this merge request

package upgrades correct as well.

I was able to get the response from the curl to the elasticsearch endpoint as well. Looks good to me.

approved this merge request

merged

mentioned in commit 0194e012

mentioned in merge request big-bang/bigbang!5260 (merged)