Serving: Enable POWER support for Knative Serving

Created on 19 Nov 2018  路  8Comments  路  Source: knative/serving

Expected Behavior

Knative Serving only support running on x86 but no POWER support yet, it would be great if Knative Serving can also run on POWER.

root@gyliu-c11:~# manifest-tool inspect gcr.io/knative-releases/github.com/knative/serving/cmd/activator@sha256:7e7abd88a292cf24a0db80d71fa16e8505dd288c241cab0b6716848f0e7fcc04
gcr.io/knative-releases/github.com/knative/serving/cmd/activator@sha256:7e7abd88a292cf24a0db80d71fa16e8505dd288c241cab0b6716848f0e7fcc04: manifest type: application/vnd.docker.distribution.manifest.v2+json
      Digest: sha256:7e7abd88a292cf24a0db80d71fa16e8505dd288c241cab0b6716848f0e7fcc04
Architecture: amd64
          OS: linux
    # Layers: 3
      layer 1: digest = sha256:8f125ded1b483229a567e48eece98cc8867c2bee55fb73e9cd65ceecc448b7c7
      layer 2: digest = sha256:d7409b568c4999bcc595709cc933f10f4c0c52b48a4ae8471a4201c41cff048c
      layer 3: digest = sha256:ee45d6e05d5b26e3702387cd7fe4925cfd54bd8981ecfbb60c06317a682c7425

/cc @zxdiscovery

arebuild kindoc kinfeature lifecyclrotten

Most helpful comment

/assign @jonjohnsonjr

This needs fat image support in ko

All 8 comments

/area build
/kind doc
/kind feature
/kind proposal

/assign @jonjohnsonjr

This needs fat image support in ko

@jonjohnsonjr @mattmoor do you think we need to enable POWER CI for this?

FWIW @seth-priya has been making progress on building knative for ppc here: https://github.com/knative/build/issues/514

We can make this significantly easier, though.

Filed a bug to track some of that work here: https://github.com/google/go-containerregistry/issues/333

Issues go stale after 90 days of inactivity.
Mark the issue as fresh by adding the comment /remove-lifecycle stale.
Stale issues rot after an additional 30 days of inactivity and eventually close.
If this issue is safe to close now please do so by adding the comment /close.

Send feedback to Knative Productivity Slack channel or file an issue in knative/test-infra.

/lifecycle stale

Stale issues rot after 30 days of inactivity.
Mark the issue as fresh by adding the comment /remove-lifecycle rotten.
Rotten issues close after an additional 30 days of inactivity.
If this issue is safe to close now please do so by adding the comment /close.

Send feedback to Knative Productivity Slack channel or file an issue in knative/test-infra.

/lifecycle rotten

Rotten issues close after 30 days of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh by adding the comment /remove-lifecycle rotten.

Send feedback to Knative Productivity Slack channel or file an issue in knative/test-infra.

/close

@knative-housekeeping-robot: Closing this issue.

In response to this:

Rotten issues close after 30 days of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh by adding the comment /remove-lifecycle rotten.

Send feedback to Knative Productivity Slack channel or file an issue in knative/test-infra.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Was this page helpful?
0 / 5 - 0 ratings