Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-17010

[fiware-stackoverflow] Deploying Keyrock Idm on Kubernetes

    Details

      Description

      Created question in FIWARE Q/A platform on 20-10-2020 at 17:10
      Please, ANSWER this question AT https://stackoverflow.com/questions/64448470/deploying-keyrock-idm-on-kubernetes

      Question:
      Deploying Keyrock Idm on Kubernetes

      Description:
      I have 2 pods(1mysql+1idm) on Kubernetes Cluster (1 master+1 worker node on VirtualBox)
      Although Keyrock creates the idm database, it cannot be migrated.
      So the superuser is never inserted into db and many fields of the tables are missing.
      Below are presented the idm's logs from the relative container:

        Activity

        Hide
        backlogmanager Backlog Manager added a comment -

        2020-10-26 09:47|CREATED monitor | # answers= 0, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2020-10-26 09:47|CREATED monitor | # answers= 0, accepted answer= False
        Hide
        backlogmanager Backlog Manager added a comment -

        2020-12-11 09:34|UPDATED status: transition Answer| # answers= 1, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2020-12-11 09:34|UPDATED status: transition Answer| # answers= 1, accepted answer= False
        Hide
        backlogmanager Backlog Manager added a comment -

        2020-12-28 12:49|UPDATED status: transition Answered| # answers= 1, accepted answer= False

        Show
        backlogmanager Backlog Manager added a comment - 2020-12-28 12:49|UPDATED status: transition Answered| # answers= 1, accepted answer= False

          People

          • Assignee:
            aalonsog Alvaro Alonso
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: