-
Notifications
You must be signed in to change notification settings - Fork 121
Added docs for EKS deployment #2785
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
Conversation
Changes to cisco asa and ftd parsers
* fix: update dell powerstore index * fix: remove change from enterprise
Signed-off-by: mstopa-splunk <[email protected]>
Signed-off-by: Ilya Kheifets <[email protected]>
| @@ -0,0 +1,80 @@ | |||
| apiVersion: apps/v1 | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we already have helm chart for microk8s. Why we cannot use it for managed k8s in AWS?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm yeah I guess we could use it to, but I was thinking about something more basic that the customer can configure themselves manually. We could also link it in this new page I guess?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but I was thinking about something more basic that the customer can configure themselves manually.
But we have really enterprise and gov level customers, I not sure that they need something like that. They expecting that all features will be available :)
the customer can configure themselves manually
Not sure that working like that, just remember expirience from on-calls. In best case they can read a doc. @sbylica-splunk they will recognise this guide like official recommendation from Splunk
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, since it's an experimental feature (and marked as such) we won't be providing direct support I think. Earlier we decided that doing a full helm chart from the start is too much of a scope for such project
| targetPort: 8080 | ||
| name: "healthcheck" | ||
| protocol: TCP | ||
| nodePort: 30080 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we also have custom ports for SC4S_LISTEN_{}_{}_PORT
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should be up to the customer to change
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sbylica-splunk I not sure that our users reading a code and know how it's working :)
Maximum they can read carefully docs, it should be on guide at least.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See above
Added experimental docs for deployment on AWS