Skip to content

Migrate to metal-apiserver - #36

Closed
majst01 wants to merge 37 commits into
mainfrom
migrate-to-metal-apiserver
Closed

majst01 wants to merge 37 commits into
mainfrom
migrate-to-metal-apiserver

Conversation

@majst01

@majst01 majst01 commented Jun 23, 2025 •

Copy link
Copy Markdown
Contributor

Description

Next microservice which gets migrated to MEP-4

Depends on:

Closes: #37

metal-hammer must now call the rest endpoint to get the configuration with the token is now:

/config/<machine-uuid>

Then pixiecore creates a token which allows calls only from this machine uuid

TODO:

  • if machine-uuid is empty do not create a token for the machine to stay compatible with existing metal-hammer
  • change deployment
  • add a helper to create proper tokens which is suitable for this service (image.list and partition.list is only required)
  • add to the endpoint which gets called from the metal-hammer a service which creates a token for this machine, even better would be to add the token to the kernel cmdline, which is limited to 4096 chars which should be enough. This would eliminate the requirement of the extra http endpoint which is actually used for the hammer -> pixiecore communication.
  • maybe also add a regular token refresh call into this service as well

@majst01
majst01 force-pushed the migrate-to-metal-apiserver branch from 33c1311 to bfb29a4 Compare February 6, 2026 07:12
@majst01
majst01 force-pushed the migrate-to-metal-apiserver branch from bfb29a4 to f8c7f2f Compare February 6, 2026 07:12
@Gerrit91

Copy link
Copy Markdown
Contributor

Was superseded by #51.

@Gerrit91 Gerrit91 closed this Sep 30, 2026
@Gerrit91
Gerrit91 deleted the migrate-to-metal-apiserver branch September 30, 2026 11:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Migrate to MEP-4

2 participants