Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

invalid header field value error when setting up with S3. #161

kishorekumark opened this issue Dec 21, 2017 · 3 comments


None yet
2 participants
Copy link

commented Dec 21, 2017

I'm not able to deploy kubed in my environment, getting following error.

I1215 17:09:05.915055 1 run.go:39] Starting kubed...
I1215 17:09:05.915149 1 run.go:57] configurations provided for kubed { /srv/kubed/config.yaml :8080 :56790 false /tmp kube-system 5m0s}
W1215 17:09:05.915183 1 client_config.go:529] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
I1215 17:09:05.916254 1 run.go:85] Running kubed watcher
[golang-sh]$ osm lc --osmconfig /tmp/osm/config.yaml
Containers, listing the buckets: RequestError: send request failed
caused by: Get net/http: invalid header field value "AWS4-HMAC-SHA256 Credential=XXXXXXX\n/20171215/us-east-1us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=YYYYYYY" for key Authorization
F1215 17:09:06.281528 1 operator.go:403] exit status 1

could you please help me how can i overcome this error?


This comment has been minimized.

Copy link

commented Dec 22, 2017

Which version of kubed are you using? Can you share the relevant portion of your config.yaml ?


This comment has been minimized.

Copy link

commented Dec 25, 2017

Using kubed:0.3.0 verison and below is the config.yml

address: :8080
enableReverseIndex: true
enableSearchIndex: true
clusterName: us-east
enableConfigSyncer: true
endpoint: ''
bucket: us-east-backup-kubed
prefix: useast1-k8s
storageSecretName: snap-secret
sanitize: true
schedule: '@every 1h'


This comment has been minimized.

Copy link

commented May 29, 2018

Should be fixed by release. Please reopen if you are still having this issue.

@tamalsaha tamalsaha closed this May 29, 2018

@tamalsaha tamalsaha added this to the 0.7.0 milestone May 29, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.