Skip to content

Conversation

mikedickey
Copy link
Contributor

No description provided.

@mikedickey
Copy link
Contributor Author

Fixes #56

Copy link
Contributor

@kelvinatsplunk kelvinatsplunk left a comment

Choose a reason for hiding this comment

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

We should be able to use nginx or haproxy too ?

@mikedickey
Copy link
Contributor Author

We should be able to use nginx or haproxy too ?

Possibly, I just haven't tested or tried those out yet.

Copy link
Contributor

@ryanfaircloth ryanfaircloth left a comment

Choose a reason for hiding this comment

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

I was not able to reproduce the TLS success. I did run into an immediate issue when patching the svc the ELB in was selects the new port as the health proper which makes all nodes out of service. I fixed that but can not make a connection

@Caldas
Copy link
Contributor

Caldas commented Apr 16, 2020

@mikedickey this is the best/recommended way to set the communication between nodes? If yes, I can test on my new cluster

@mikedickey
Copy link
Contributor Author

@mikedickey this is the best/recommended way to set the communication between nodes? If yes, I can test on my new cluster

We use Istio at Splunk, and it seems to have most traction. Doesn't mean you can't use something else, but we will likely continue to focus on it for examples, testing, etc.

@mikedickey mikedickey closed this Apr 17, 2020
@mikedickey mikedickey reopened this Apr 17, 2020
@mikedickey mikedickey merged commit eb4635a into develop Apr 17, 2020
@mikedickey mikedickey deleted the istio-for-tls-s2s branch April 17, 2020 00:54
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.

4 participants