RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

The kubernetes plugin is extremely slow when run on a cluster with thousands of namespaces. This is the result of multiple kubectl commands being executed per project. There should be a way to supress this behavior.

See https://github.com/sosreport/sos/pull/1068 for a solution of this which adds a new option to the kubernetes module to suppress this behavior.

Version-Release number of selected component (if applicable):


How reproducible:
na

Steps to Reproduce:
1.na
2.
3.

Actual results:
kubernetes plugin takes a long time to complete when running a sosreport.

Expected results:
expect to be able to suppress some of this behavior that allows the sosreport to run in a reasonable time. 

Additional info:

The pull request for this is already in progress: if anything, I am considering flipping the default (so that all namespaces will _not_ be collected by default - i.e. the user has to enable an option in order to get the current behaviour).

This will mean that associates will need to request the "all namespaces" option when appropriate but this seems a preferable user experience to defaulting to collecting this - on systems with many namespaces where sos is being run for an unrelated problem this would be quite irritating.

(based on prior experience, users will not learn to add '-k kubernetes.no_individual' until they have at least one bad experience with the default behaviour).

That sounds like a good idea to me. Once a solution is in place, if it changes any support workflows, I can modify our docs. 

Thanks,
Evan Mahoney

Fixed via sos 3.5 rebase.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:0963