Task Description (Required)

Tracking issue for the work required to release the AI catalog blog post:

• Doc review (if available)
• Marketing review (follow up on thread on #rhdh-marketing)
• Cut branch on https://github.com/redhat-ai-dev/model-catalog (will be renamed to model-catalog-exxample), and update blog post to point to branch
  • Take snapshot of catalog repository traffic (and forks) before publishing, and after (weekly update?)
• Release on developers.redhat.com (blog posting guidelines here: https://docs.google.com/document/d/12gsW4wBcJBg9lBFE90mwa4mrex4DTAYw0sA84q94sc4/edit)
• Announce blog post (RHDH newsletter? Ben or RHDH marketing folks may have ideas)
• Aim to release right before KubeCon

Change Request 

<Select which item is being changed>

[ ]  Add New Tokens

[ ]  Rotate Tokens

[ ]  Remove Tokens

[ ] Others: (specify)

  Environment

<Select which environment the change is being made on.  If both, open a separate issue so changes are tracked in each environment>

[ ]  Stage OR

[ ]  Prod

  Backout Plan

<State what steps are needed to roll back in case something goes wrong>

  Downtime

<Is there any downtime for these changes?  If so, for how long>

  Risk Level

<How risky is this change?>

  Testing

<How are changes verified?>

  Communication

<How are service owners or consumers notified of these changes?>