Skip to content

Conversation

@sbylica-splunk
Copy link
Contributor

Added experimental docs for deployment on AWS

Base automatically changed from develop to main August 4, 2025 12:52
@ajasnosz ajasnosz changed the base branch from main to develop August 4, 2025 12:53
@sbylica-splunk sbylica-splunk requested a review from ajasnosz August 5, 2025 07:07
@@ -0,0 +1,80 @@
apiVersion: apps/v1
Copy link
Contributor

@ikheifets-splunk ikheifets-splunk Aug 6, 2025

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?

Copy link
Contributor Author

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?

Copy link
Contributor

@ikheifets-splunk ikheifets-splunk Aug 7, 2025

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

Copy link
Contributor Author

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
Copy link
Contributor

@ikheifets-splunk ikheifets-splunk Aug 6, 2025

Choose a reason for hiding this comment

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

Copy link
Contributor Author

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

Copy link
Contributor

@ikheifets-splunk ikheifets-splunk Aug 7, 2025

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.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

See above

@sbylica-splunk sbylica-splunk merged commit 4b5c9d6 into develop Aug 11, 2025
18 of 23 checks passed
@sbylica-splunk sbylica-splunk deleted the docs/eks_deployment branch August 11, 2025 12:16
@github-actions github-actions bot locked and limited conversation to collaborators Aug 11, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants