Site controller access point management for the sk2 platform

[fgiorgetti]

No description provided.

[JPadovano1483]

@fgiorgetti One thing that I was initially having some issues with was that selecting multiple accesspoints was finicky for me. If I initially selected a manage and van access point and then bootstrapped the site, it created the resources I would expect to see in the site namespace (i.e. networkaccess and route), but the management controller did not process it. What I was left with was a manage accesspoint with a host and port and a hanging van accesspoint. If I created a new accesspoint after this though, it would then process both the van and the new access points, giving them a host and port. It seems like this may be a timing issue of when the manage accesspoint is ready. This happened a few times, but I have been unable to consistently replicate it and all the access points have processed normally the past few times I've tried.

Other than that, I didn't run into any issues and the v2 functionality seems to work well. One other question, should we change the site controller image that we set in db-setup.sql to your new image?

[fgiorgetti]

@JPadovano1483 I have noticed that sync issue with the management controller, if the site-controller or its router pod got restarted. Which was solved when I restarted the management controller pod. I will try to reproduce it, to see if I can spot the reason for. But once the management controller is connected to the AMQP BUS, I am not experiencing any issue.

One other question, should we change the site controller image that we set in db-setup.sql to your new image?

What if we add a github actions workflow to start building and pushing the images to quay.io on PRs merged to main branch? This way we could have them under quay.io/skupper?

[JPadovano1483]

@fgiorgetti yes, I think that would be a good idea.

[fgiorgetti]

@JPadovano1483 Latest commit fixes the issue causing the 409 error (already exists), as it was trying to recreate an existing RouterAccess.