image deprecation

---

⚠️ DEPRECATION NOTICE
As of June 24th, 2025:
(Latest Release 1.2.3).

• Timeline:
  • ~ 60 days for GitHub Code Archive -> https://github.com/splunk/fluent-plugin-kubernetes-objects
  • ~ 30 days for DockerHub Image Removal -> https://hub.docker.com/repository/docker/splunk/kube-objects/general
• Maintenance:
  • Anyone actively using this code please Fork it.
  • Anyone intererested in maintaining the Repository, raise a Pull Request for CODEOWNERS.
    • We will then proceed to review the request internally.

---

Fluent Plugin Kubernetes Objects v1.2.3

What's Changed

• Fix vulnerabilities

Full Changelog: v1.2.2...1.2.3

Fluent Plugin Kubernetes Objects v1.2.2

What's Changed

• Security fixes

Full Changelog: 1.2.1...v1.2.2

Fluent Plugin Kubernetes Objects v1.2.1

What's Changed

• Security update

Fluent Plugin Kubernetes Objects v1.2.0

What's Changed

• Bump yajl-ruby from 1.4.2 to 1.4.3 by @harshit-splunk in #93
• Bumped rack to v2.2.3.1 by @harshit-splunk in #94
• Add fossa and semgrep by @aryznar-splunk in #95
• Updated kubeclient by @harshit-splunk in #96

New Contributors

• @aryznar-splunk made their first contribution in #95

Full Changelog: 1.1.12...1.2.0

Fluent Plugin Kubernetes Objects v1.1.12

Release Highlight

• Library upgrade for security fix

Full Changelog: 1.1.11...1.1.12

Fluent Plugin Kubernetes Objects v1.1.11

What's Changed

• fixed broken yum command on docker image by @harshit-splunk in #86

Full Changelog: 1.1.9...1.1.11

Fluent Plugin Kubernetes Objects v1.1.10

What's Changed

• stop pull/watch thread when resource not found by @harshit-splunk in #78
• Upgraded gems to fix security vulnerabilities

Full Changelog: 1.1.9...1.1.10

Fluent Plugin Kubernetes Objects v1.1.9

What's Changed

• upgrading fluentd-hec gem version to 1.2.9

Fluent Plugin Kubernetes Objects v1.1.8

Release Highlight

• Added support for multiple architectures (ARM64 & AMD64)
• Library upgrade for security fix

New Contributors

• @mwang2016 made their first contribution in #65
• @foram-splunk made their first contribution in #69
• @hbrewster-splunk made their first contribution in #70