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.

Sign up for GitHub

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

Jump to bottom

CONTENT_ORIGIN set to use https when no ingress_tls_secret provided #1048

Closed
dkliban opened this issue Aug 16, 2023 · 0 comments · Fixed by #1050
Closed

CONTENT_ORIGIN set to use https when no ingress_tls_secret provided #1048

dkliban opened this issue Aug 16, 2023 · 0 comments · Fixed by #1050
Assignees
@dkliban
Labels
Issue Triage-Needed

Comments

@dkliban
Copy link
Member

dkliban commented Aug 16, 2023

I noticed that the ingress is configured to expose port 80, Pulp's settings have content origin set to https://{ingress_host}.
@dkliban dkliban mentioned this issue Aug 17, 2023
Merged
dkliban added a commit to dkliban/pulp-operator that referenced this issue Aug 17, 2023
@dkliban
Fixes bug related to CONTENT_ORIGIN scheme always being https
4062fee 
fixes: pulp#1048
@dkliban dkliban self-assigned this Aug 17, 2023
dkliban added a commit to dkliban/pulp-operator that referenced this issue Aug 17, 2023
@dkliban
Fixes bug related to CONTENT_ORIGIN scheme always being https
979a8c4 
fixes: pulp#1048
openshift-merge-robot pushed a commit that referenced this issue Aug 17, 2023
@dkliban @openshift-merge-robot
Fixes bug related to CONTENT_ORIGIN scheme always being https
4915d57 
fixes: #1048
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dkliban dkliban

Labels
Issue Triage-Needed
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fixes bug related to CONTENT_ORIGIN scheme always being https dkliban/pulp-operator
1 participant
@dkliban