Commits on Aug 8, 2024

1. Available CRDs check feature …

   Reasons for this enhancement:
   - A controller cannot set up a watch for a CRD that is not installed on
    the cluster, trying to set up a watch will panic the operator
   - There is no known way, that we are aware of, to add a watch later
    without client cache issue
   
   How does the enhancement work around the issue:
   - A new controller to watch creation/deletion for the CRDs of interest
    to prevent unnecessary reconciles
   - On start of the operator(main), detect which CRDs are avail (out of a
    fixed list)
   - At the start each reconcile of new controller, we fetch the CRDs
    available again and compare it with CRDs fetched in previous step,
     If there is any change, we panic the op
   
   Signed-off-by: raaizik <132667934+raaizik@users.noreply.github.com>
   Co-Authored-By: Rewant Soni <rewant.soni@gmail.com>

   

   raaizik and rewantsoni committed Aug 8, 2024
   Configuration menu

   • View commit details
   • Copy full SHA for e5d154b
   • Browse repository at this point

   Copy the full SHA

   e5d154b View commit details

   Browse the repository at this point in the history

2. Available CRDs check feature w script …

   Adds a script that bypasses pod restarts
   
   Signed-off-by: raaizik <132667934+raaizik@users.noreply.github.com>
   Co-Authored-By: Rewant Soni <rewant.soni@gmail.com>

   

   raaizik and rewantsoni committed Aug 8, 2024
   Configuration menu

   • View commit details
   • Copy full SHA for 3617868
   • Browse repository at this point

   Copy the full SHA

   3617868 View commit details

   Browse the repository at this point in the history