spinnaker
Unable to see custom banner in spinnaker UI
We are using spinnaker version 1.38.0 and managing spinnaker via halyard. We have put banner configuration in settings-local.js and deploy but the banner is not visible in spinnaker UI.
window.spinnakerSettings = { banner: { id: 'maintenance', message: 'Scheduled maintenance on July 5th, 2025, from 2 AM to 4 AM UTC.', type: 'info', // Options: 'info', 'warning', 'error' link: 'https://status.example.com', enabled: true, } };
I can see the configuration in deck in /opt/spinnaker
For help, it'd be worth pinging in the spinnaker slack or information on things like this! This.. MAY be a misconfiguration but I've not looked at the banner much... we have some code we're considering pushing up that supports a global banner type thing but I THINK the current "banner" stuff maybe wasn't quite as functional as others? @christosarvanitis had some work there or maybe comments... still slack better place probably or this!
So right now OSS deck doesnt have the functionality out of the box to render and post global banners. This SETTINGS.banners configuration can be used given that the user will create their own custom banners and import them on their own fork/build. See https://github.com/spinnaker/deck/pull/8735
Internally we developed a plugin that exposes a CRUD endpoint in Gate for banners and storing them in gate's Redis. Deck queries gate for that information in intervals and then renders the active banners. When I get some free time i could try to contribute this functionality to OSS if this is something of interest
This issue hasn't been updated in 45 days, so we are tagging it as 'stale'. If you want to remove this label, comment:
@spinnakerbot remove-label stale
This issue is tagged as 'stale' and hasn't been updated in 45 days, so we are tagging it as 'to-be-closed'. It will be closed in 45 days unless updates are made. If you want to remove this label, comment:
@spinnakerbot remove-label to-be-closed
This issue is tagged as 'to-be-closed' and hasn't been updated in 45 days, so we are closing it. You can always reopen this issue if needed.