Skip to content

Add end of support notice for byoe #2805

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.

Sign up for GitHub

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

Merged
pdudhaiya-crest merged 2 commits into from
Oct 21, 2025
Merged

Add end of support notice for byoe #2805

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ecffc13
docs: add end of support notice for BYOE deployments
pdudhaiya-crest Oct 16, 2025
4015935
docs: formatting changes
pdudhaiya-crest Oct 16, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/gettingstarted/byoe-rhel8.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,11 @@
# Configure SC4S in a non-containerized SC4S deployment

!!! warning ""
Support for all non-containerized deployments using the "bring your own environment" method, as detailed in this documentation, will end in **April 2026**.
After that, no further updates, security patches, or technical support will be provided for this deployment method. Continued use may expose your environment to security risks and compatibility issues.

We recommend planning your migration to one of the other supported platform or deployment method before April 2026 to ensure continued support and security. See [Select a Container Runtime and SC4S Configuration](https://splunk.github.io/splunk-connect-for-syslog/main/gettingstarted/getting-started-runtime-configuration/#step-3-select-a-container-runtime-and-sc4s-configuration) for more details.

Configuring SC4S in a non-containerized SC4S deployment requires a custom configuration. Note that since Splunk does not control your unique environment, we cannot help with setting up environments, debugging networking, etc. Consider this configuration only if:
Copy link
Contributor

@sbylica-splunk sbylica-splunk Oct 16, 2025

Choose a reason for hiding this comment

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

We could bold or otherwise make more visible the line that states that we cannot help with setup.

Copy link
Contributor Author

@pdudhaiya-crest pdudhaiya-crest Oct 16, 2025

Choose a reason for hiding this comment

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

@sbylica-splunk Made the changes and updated the screenshot in this PR.


* Your specific requirements preclude the use of containers or demand that you use SC4S in a custom environment.
Expand Down
2 changes: 1 addition & 1 deletion docs/gettingstarted/getting-started-runtime-configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ Check your Podman or Docker documentation to see which operating systems are sup
| [Docker CE + systemd](docker-systemd-general.md) | |
| [Docker Desktop + Compose](docker-compose-MacOS.md) | MacOS |
| [Docker Compose](docker-compose.md) | |
| [Bring your own Environment](byoe-rhel8.md) | RHEL or CentOS 8.1 & 8.2 (best option) |
| (Deprecated) [Bring your own Environment](byoe-rhel8.md) | RHEL or CentOS 8.1 & 8.2 (best option) |
| [Offline Container Installation](docker-podman-offline.md) | |
| [Ansible+Docker Swarm](ansible-docker-swarm.md) | |
| [Ansible+Podman](ansible-docker-swarm.md) | |
Expand Down
1 change: 1 addition & 0 deletions mkdocs.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,7 @@ markdown_extensions:
format: !!python/name:pymdownx.superfences.fence_code_format
- pymdownx.blocks.tab:
alternate_style: true
- admonition


theme:
Expand Down
Loading