Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default Deny Egress prevents Solrcloud from starting #82

Open
2 tasks
nickumia-reisys opened this issue Feb 6, 2023 · 0 comments
Open
2 tasks

Default Deny Egress prevents Solrcloud from starting #82

nickumia-reisys opened this issue Feb 6, 2023 · 0 comments

Comments

@nickumia-reisys
Copy link
Contributor

EKS Brokerpak @ https://github.com/GSA/datagov-brokerpak-eks/tree/113dfdac3399372b672f88145dc32470e47d5251

How to reproduce

  1. Deploy EKS Cluster
  2. Connect ssb-solrcloud to cluster.
  3. Try to provision a solrcloud cluster.

Expected behavior

Solrcloud provisioning succeeded.

Actual behavior

Zookeeper cannot start because it fails a liveliness probe (probably initiated by the solr node)

Sketch

  • Modify/Add a network policy in the datagov-brokerpak-solr repo to allow egress traffic within solrcloud cluster
  • Figure out a way to test it. (Technically an integration test, but maybe just add a default deny egress policy to the datagov-brokerpak-solr repo to mirror the one that gets created in the datagov-brokerpak-eks repo.
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

No branches or pull requests

1 participant