Skip to content

Conversation

@Kamalesh-Seervi
Copy link

@Kamalesh-Seervi Kamalesh-Seervi commented Oct 27, 2025

Proposed changes

  • This is the issue link I worked in it to fix the litmus logo with Kubernetes Logo..

Here's a concise summary for your PR description:

#5284


Replaced the Litmus logo with the Kubernetes logo for all 30 Kubernetes fault cards in the ChaosHub.

Changes Made

File Modified: ChaosFaults.tsx

What Changed:

  • Added imports for config and getScope utilities to access API endpoints and project context
  • Updated the FaultCard component to conditionally render fault icons:
    • Kubernetes faults now display the Kubernetes logo loaded from the backend API
    • Other fault categories (AWS, Azure, GCP, etc.) continue to display the Litmus logo
  • The Kubernetes logo is fetched dynamically using the same endpoint pattern used elsewhere in the application

Implementation Details:

// Before
<Icon size={23} name="chaos-litmuschaos" />

// After
{fault.chartName.toLowerCase() === 'kubernetes' ? (
  <img
    src={`${config.restEndpoints?.chaosManagerUri}/icon/default/${hubName}/${fault.chartName}/${fault.name}.png`}
    alt={`${fault.name} icon`}
    style={{ width: 23, height: 23 }}
  />
) : (
  <Icon size={23} name="chaos-litmuschaos" />
)}

Testing

  • ✅ Lint checks passed
  • Kubernetes fault cards now display the appropriate Kubernetes logo
  • Other fault categories remain unchanged with the Litmus logo

Types of changes

What types of changes does your code introduce to Litmus? Put an x in the boxes that apply

  • New feature (non-breaking change which adds functionality)
  • Bugfix (non-breaking change which fixes an issue)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (if none of the other choices applies)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

  • I have read the CONTRIBUTING doc
  • I have signed the commit for DCO to be passed.
  • Lint and unit tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works (if appropriate)
  • I have added necessary documentation (if appropriate)

Dependency

  • Please add the links to the dependent PR need to be merged before this (if any).

Special notes for your reviewer:

Signed-off-by: Kamalesh-Seervi <[email protected]>
@PriteshKiri
Copy link
Contributor

Hey @Kamalesh-Seervi

Could you please resolve the conflicts? Please refer this PR for the same

@Kamalesh-Seervi
Copy link
Author

Made better fix the gcp logo faults value was hardcoded I made it standard and resolved conflicts

@PriteshKiri
Copy link
Contributor

Hey @Kamalesh-Seervi
Could you please share a screenshot with your proposed solution?

Actually, a video on navigating between Kubernetes and GCP faults would be good.

@Kamalesh-Seervi
Copy link
Author

Screen.Recording.2025-11-02.at.11.00.24.PM.mov

@PriteshKiri
Copy link
Contributor

Thanks for sharing the video. Could you please resolve the conflicts?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants