Skip to content

Conversation

@camilamacedo86
Copy link
Contributor

@camilamacedo86 camilamacedo86 commented Nov 19, 2024

This change respects developers' environments and preferences by prioritizing the globally installed kind binary for managing Kubernetes clusters. It reduces potential conflicts and debugging issues, ensuring better compatibility with existing setups.

Scenarios Addressed

  1. Image Loading Issues:
    • Using a BINGO-installed kind binary caused images to load into the wrong cluster, leading to debugging delays.
  2. Hidden Clusters:
    • Clusters created with the BINGO-managed kind were not visible in the global kind context, causing resource leaks and confusion.

Proposed Solution

  • Check for a globally installed kind binary and use it if available.
  • Fallback to the BINGO-managed kind binary only when no global version is detected.
  • Provide clear messaging about the binary being used.

Benefits

  • Respects developers' preferences and existing environments.
  • Prevents unnecessary debugging and resource leaks.
  • Aligns with standard workflows while maintaining BINGO compatibility.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 19, 2024
@netlify
Copy link

netlify bot commented Nov 19, 2024

Deploy Preview for olmv1 ready!

Name Link
🔨 Latest commit 16923f6
🔍 Latest deploy log https://app.netlify.com/sites/olmv1/deploys/673bd9ce267dce00088ec3be
😎 Deploy Preview https://deploy-preview-1481--olmv1.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@camilamacedo86 camilamacedo86 changed the title feat: prioritize global kind binary over BINGO-managed version feat: Prioritize Global kind Binary Over BINGO-Managed Version Nov 19, 2024
…ritizing the globally installed `kind` binary for managing Kubernetes clusters. It reduces potential conflicts and debugging issues, ensuring better compatibility with existing setups.

1. **Image Loading Issues**:
   - Using a BINGO-installed `kind` binary caused images to load into the wrong cluster, leading to debugging delays.
2. **Hidden Clusters**:
   - Clusters created with the BINGO-managed `kind` were not visible in the global `kind` context, causing resource leaks and confusion.

- Check for a globally installed `kind` binary and use it if available.
- Fallback to the BINGO-managed `kind` binary only when no global version is detected.
- Provide clear messaging about the binary being used.

- Respects developers' preferences and existing environments.
- Prevents unnecessary debugging and resource leaks.
- Aligns with standard workflows while maintaining BINGO compatibility.
@camilamacedo86 camilamacedo86 marked this pull request as ready for review November 19, 2024 00:20
@camilamacedo86 camilamacedo86 requested a review from a team as a code owner November 19, 2024 00:20
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 19, 2024
@camilamacedo86 camilamacedo86 changed the title feat: Prioritize Global kind Binary Over BINGO-Managed Version 🌱 feat: Prioritize Global kind Binary Over BINGO-Managed Version Nov 19, 2024
@codecov
Copy link

codecov bot commented Nov 19, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.73%. Comparing base (e5820ae) to head (16923f6).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1481   +/-   ##
=======================================
  Coverage   74.73%   74.73%           
=======================================
  Files          42       42           
  Lines        3241     3241           
=======================================
  Hits         2422     2422           
  Misses        646      646           
  Partials      173      173           
Flag Coverage Δ
e2e 52.42% <ø> (ø)
unit 57.20% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.


🚨 Try these New Features:

@camilamacedo86 camilamacedo86 changed the title 🌱 feat: Prioritize Global kind Binary Over BINGO-Managed Version 🌱 feat: Prioritize Global kind Installation Over BINGO-Managed Version Nov 19, 2024
Copy link
Member

@m1kola m1kola left a comment

Choose a reason for hiding this comment

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

.bingo/Variables.mk is auto-generated. We can't edit it (see notice at the top of the file).

@camilamacedo86
Copy link
Contributor Author

Hi @m1kola

.bingo/Variables.mk is auto-generated. We can't edit it (see notice at the top of the file).

It worked locally. But if it is autogenerated, it will be lost
Oh, that changes a lot of things
So, has no way to implement it with BINGO
Is there no place where I can say the same for BINGO?

@camilamacedo86
Copy link
Contributor Author

Closing this one

@camilamacedo86 camilamacedo86 deleted the use-global-kind branch November 19, 2024 12:28
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.

2 participants